table of contents
PEGASUS-KEG(1) | Pegasus Manual | PEGASUS-KEG(1) |
NAME¶
pegasus-keg - kanonical executable for grids
SYNOPSIS¶
pegasus-keg [-a appname] [-t interval |-T interval] [-l logname]
[-P prefix] [-o fn [..]] [-i fn [..]] [-G sz]
[-C] [-e env [..]] [-p parm [..]]
DESCRIPTION¶
The kanonical executable is a stand-in for regular binaries in a DAG - but not for their arguments. It allows to trace the shape of the execution of a DAG, and thus is an aid to debugging DAG related issues.
Key feature of pegasus-keg is that it can copy any number of input files, including the generator case, to any number of output files, including the datasink case. In addition, it protocols the IPv4 and hostname of the host it ran upon, the current timestamp, and the run time from start til the point of logging the information, the current working directory and some information on the system environment. pegasus-keg will also report all input files, the current output files and any requested string and environment value.
ARGUMENTS¶
The -e, -i, -o and -p arguments allow lists with arbitrary number of arguments. These options may also occur repeatedly on the command line. The file options may be provided with the special filename - to indicate stdout in append mode for writing, or stdin for reading. The -a, -l , -P , -T and -t arguments should only occur a single time with a single argument.
If pegasus-keg is called without any arguments, it will display its usage and exit with success.
-a appname
-e env [..]
-i infile [..]
-l logfile
-o outfile [..]
-G size
-C
-p string [..]
-P prefix
-t interval
-T interval
RETURN VALUE¶
Execution as planned will return 0. The failure to open an input file will return 1, the failure to open an output file, including the log file, will return with exit code 2.
EXAMPLE¶
The example shows the bracketing of an input file, and the copy produced on the output file. For illustration purposes, the output file is connected to stdout :
$ date > xx $ pegasus-keg -i xx -p a b c -o - --- start xx ----
Thu May 5 10:55:45 PDT 2011 --- final xx ---- Timestamp Today: 20110505T105552.910-07:00 (1304618152.910;0.000) Applicationname: pegasus-keg [3661M] @ 128.9.xxx.xxx (xxx.isi.edu) Current Workdir: /opt/pegasus/default/bin/pegasus-keg Systemenvironm.: x86_64-Linux 2.6.18-238.9.1.el5 Processor Info.: 4 x Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz @ 2660.068 Load Averages : 0.298 0.135 0.104 Memory Usage MB: 11970 total, 8089 free, 0 shared, 695 buffered Swap Usage MB: 12299 total, 12299 free Filesystem Info: / ext3 62GB total, 20GB avail Filesystem Info: /lfs/balefire ext4 1694GB total, 1485GB avail Filesystem Info: /boot ext2 493MB total, 447MB avail Output Filename: - Input Filenames: xx Other Arguments: a b c
RESTRICTIONS¶
The input file must be textual files. The behaviour with binary files is unspecified.
The host address is determined from the primary interface. If there is no active interface besides loopback, the host address will default to 0.0.0.0. If the host address is within a virtual private network address range, only (VPN) will be displayed as hostname, and no reverse address lookup will be attempted.
The processor info line is only available on Linux systems. The line will be missing on other operating systems. Its information is assuming symmetrical multi processing, reflecting the CPU name and speed of the last CPU available in /dev/cpuinfo .
There is a limit of 4 * page size to the output buffer of things that .B pegasus-keg can report in its self-info dump. There is no such restriction on the input to output file copy.
AUTHORS¶
Jens-S. Vöckler <voeckler at isi dot edu>
Mike Wilde
Yong Zhao
Pegasus - http://pegasus.isi.edu/
11/09/2018 | Pegasus 4.4.0 |