rancid_par(1) [debian man page]

rancid_par(1)						      General Commands Manual						     rancid_par(1)

NAME

       rancid_par - parallel command processing

SYNOPSIS

       rancid_par [-dfiqx] [-c	command] [-l  logfile] [-n #] file [file...]

DESCRIPTION

       rancid_par  takes  a  list  of  files  to run a command on.  The first line of each file begins with a colon (:) or a pound-sign (#).  If a
       colon, the remainder of the line is a command to run for each of the subsequent lines.  If a pound-sign, then each  subsequent  line  is  a
       (self-contained)  command,  unless  the -c option was specified, in which case it operates as if the argument to -c had followed a colon on
       the first line.

       In each of the cases where the lines of the file following the first are not commands (i.e.: colon or -c), instances of	open-close  braces
       ({}) in the command will be replaced by these values.

       For example, a inputfile whose contents is:

	    : echo {}
	    a
	    b
	    c

       run with rancid_par like so:

	    %rancid_par -q inputfile

       will produce the following output (order will vary):

	    b
	    a
	    c

       The command-line options are as follows:

       -c     Command to be run on each of the arguments following the command-line options, where the first line of the input file(s) begins with
	      a pound-sign (#).

       -d     Print debugging information on standard error (stderr).

       -f     No file or STDIN, just run a quantity of the command specified with -c.

       -i     Run commands interactively through (multiple) xterm(1) processes.

       -l     Prefix of logfile name, as in prefix.N where N is the rancid_par process number ([0..]).

	      Default: par.log.<time>.[0..]

       -n     Number of simultaneous processes.

	      Default: 3

       -q     Quiet mode.  Do not log anything.  -q is mutually exclusive with the -x and -l options and  the  option  appearing  last	will  take
	      precedence.

       -x     View rancid_par logs in real-time via an xterm(1).

FILES

       par.log.T.N Log file; where T is the current time in seconds since the
       epoch and N is the rancid_par process number ([0..]).

								 18 December 2007						     rancid_par(1)

log(8)							      System Manager's Manual							    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 <command> 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 environment, 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  exe-
       cutable 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)