sb2-logz(1) [debian man page]

sb2-logz(1)							 sb2-logz man page						       sb2-logz(1)

NAME

       sb2-logz - sb2 log postprocessing tool

SYNOPSIS

       sb2-logz [options] < logfile

DESCRIPTION

       sb2-logz  reads	logs  created  by scratchbox2 and writes summaries (the log files can be really huge, and manually digging out information
       from them might be a time-consuming task).

       Logs are produced when sb2 is executed with -d (debug) or -L options (e.g. "-L info")

OPTIONS

       -b     no blacklist: do not ignore log lines from functions like __xstat() (there is a built-in blacklist, which tries to minimize  "noise"
	      caused by various libraries and scratchbox2 itself)

       -B fn1,fn2,..
	      blacklist funcions fn1,fn2,..: ignore lines generated by the listed library calls.

       -d level
	      debug mode, for debugging the script itself.

       -h     show help text.

       -i     print details about 'disabled' pathnames (unmodifed paths, because mapping was momentarily disabled)

       -l     print long details (affects output of -i,-m,-r,-p etc)

       -m     print details about mapped pathnames (src->dest)

       -N     print all 'notice' messages

       -p     print details about passed pathnames ('passed path' = not mapped)

       -r     print reversed mappings (dest->src)

       -s     print process statistics

       -v     verbose mode, prints dots while reading input etc.

       -P file.dot
	      write process diagram to file.dot (postprocess it with 'dot', e.g. 'dot -Tpdf file.dot >file.pdf'

       -E file.dot
	      write execution diagram to file.dot (postprocess it with 'dot', e.g. 'dot -Tpdf file.dot >file.pdf'

       -A acct-file
	      Read process accounting information from acct-file (enhances output of -P and -E)'

BUGS

       Option -A requires an accounting log, which has to be activated separately.  Generation of accounting information typically requires super-
       user privileges (or CAP_SYS_PACCT capability on Linux).	This is an system-level  restriction,  and  not  fault	of  scratchbox2.  However,
       sb2-logz  has  some  limitations:  Correlating  information from the accounting log is based on process ids, and the heuristics may fail if
       there were really many processes; The -P, -E and -A options may be less useful for longer  runs.  Best  results	are  achieved  if  process
       accounting  is  switched on just before the scratchbox2 session is created, and switched off afterwards - and there is nothing else running
       on the host at the same time.

SEE ALSO

       sb2(1), sb2-config(1), sb2-init(1), acct(2), dot(1) ( dot belongs to the graphviz package)

AUTHOR

       Lauri Aarnio

2.2								 17 December 2010						       sb2-logz(1)

LASTCOMM(1)						    BSD General Commands Manual 					       LASTCOMM(1)

NAME

     lastcomm -- show last commands executed

SYNOPSIS

     lastcomm [-EScesu] [-f file] [+format] [command ...] [user ...] [terminal ...]

DESCRIPTION

     The lastcomm utility gives information on previously executed commands.  With no arguments, lastcomm prints information about all the com-
     mands recorded during the current accounting file's lifetime.

     The following options are available:

     -E      Print the time the process exited.

     -S      Print the time the process started.

     -c      Print the amount of cpu time used by the process.

     -e      Print the amount of elapsed time used by the process.

     -s      Print the amount of system time used by the process.

     -u      Print the amount of user time used by the process.

     -f file
	     Read from file rather than the default /var/account/acct.	If file is a single dash ('-') lastcomm reads accounting entries from the
	     standard input.

     An operand with a leading plus sign ('+') is followed a user-defined format string which specifies the format in which to display the
     process's start or exit date and time.  The format string may contain any of the conversion specifications described in the strftime(3) man-
     ual page, as well as arbitrary text.

     If no options are specified, -cS is assumed.  If lastcomm is invoked with arguments, only accounting entries with a matching command name,
     user name, or terminal name are printed.  For example:

	   lastcomm a.out root ttyd0

     would produce a listing of all the executions of commands named a.out by user root on the terminal ttyd0.

     For each process entry, the following are printed.

	   o   The name of the user who ran the process.
	   o   Flags, as accumulated by the accounting facilities in the system.
	   o   The command name under which the process was called.
	   o   The amount of CPU (-c), wall (-e), system (-s), or user (-u) time used by the process (in seconds).
	   o   The time the process started (-S) or exited (-E).

     The flags are encoded as follows: ``S'' indicates the command was executed by the super-user, ``F'' indicates the command ran after a fork,
     but without a following exec(3), ``D'' indicates the command terminated with the generation of a core file, and ``X'' indicates the command
     was terminated with a signal.

     By default, accounting entries are printed going backwards in time, starting from the time lastcomm was executed.	However, if lastcomm reads
     entries from its standard input, then entries are printed in the order they are read.

FILES

     /var/account/acct	default accounting file

EXAMPLES

     The command
	   lastcomm -Ee
     will print the exit time and elapsed time of each command logged in /var/account/acct, while
	   tail -f -c 0 /var/account/acct | lastcomm -f -
     will print details of each terminating command.

SEE ALSO

     last(1), sigaction(2), strftime(3), acct(5), core(5)

HISTORY

     The lastcomm command appeared in 3.0BSD.

BSD
								   May 17, 2012 							       BSD