Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   12896 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

log(8)									log(8)

NAME
       log - Records input and output from a program

SYNOPSIS
       /usr/sbin/log <logfile> <command>

OPERANDS
       The  file in which to record the interaction being logged.  The command
       to execute.

DESCRIPTION
       The log program runs <command> and logs the input to  and  output  from
       <command>  to  the  <logfile>  file.  Input and output are logged until
       <command> exits, the log program exits, and the exit  status  of	 <com‐
       mand> is returned.

       The  log	 program  is used by the system installation procedure and the
       it(8)   command	 to   create   the   /var/adm/smlogs/install.log   and
       /var/adm/smlogs/it.log installation log files.

RESTRICTIONS
       Because the log program is used in the installation standalone environ‐
       ment, program size was the greatest concern in its implementation.  The
       log  program  does not search for the PATH variable to locate <command>
       and error messages are terse.

       The log program causes <command> to take standard input from and	 write
       standard	 output	 and standard error to UNIX pipes.  Some commands will
       not be able to operate in this environment; therefore, it is  suggested
       that you use the script(1) command instead.  UNIX shells will not issue
       prompts when run from log unless the shell is started with an  explicit
       interactive  switch  (-i	 for  most  shells).  For example, log foo.tmp
       /sbin/sh -i

       In the previous example, foo.tmp is the name of <logfile>.

       The log program intercepts  end-of-file	(usually  Ctrl/d).   Therefore
       programs	 which	normally  receive  end-of-file as an exit command must
       exit by some other means.

ERRORS
       Log open error

	      Explanation:

	      The log program was unable to open <logfile>.  Verify  that  the
	      directory	 exists	 and  that  ownerships and permissions are set
	      correctly.  Exec Error

	      Explanation:

	      The log program was unable to execute <command>. Verify that you
	      specified a full pathname for <command> and that <command> is an
	      executable file.	Fork Error

	      Explanation:

	      The log program was unable to create one	of  the	 processes  it
	      requires to log data.

SEE ALSO
       Commands: it(8), script(1)

									log(8)

                             _         _         _ 
                            | |       | |       | |     
                            | |       | |       | |     
                         __ | | __ __ | | __ __ | | __  
                         \ \| |/ / \ \| |/ / \ \| |/ /  
                          \ \ / /   \ \ / /   \ \ / /   
                           \   /     \   /     \   /    
                            \_/       \_/       \_/ 

Vote for polarhome