Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pegasus-invoke(1) [debian man page]

PEGASUS-INVOKE(1)														 PEGASUS-INVOKE(1)

NAME
pegasus-invoke - invokes a command from a file SYNOPSIS
pegasus-invoke ( app | @fn ) [ arg | *@fn [..]] DESCRIPTION
The pegasus-invoke tool invokes a single application with as many arguments as your Unix permits (128k characters for Linux). Arguments are come from two places, either the command-line as regular arguments, or from a special file, which contains one argument per line. The pegasus-invoke tool became necessary to work around the 4k argument length limit in Condor. It also permits to use arguments inside argument files without worry about shell, Condor or Globus escape necessities. All argument file contents are passed as is, one line per argument entry. ARGUMENTS
-d This option increases the debug level. Currently, only debugging or no debugging is distinguished. Debug message are generated on stdout . By default, debugging is disabled. -h This option prints the help message and exits the program. -- This option stops any option processing. It may only be necessary, if the application is stated on the command-line, and starts with a hyphen itself.The first argument must either be the application to run as fully-specified location (either absolute, or relative to current wd), or a file containing one argument per line. The PATH environment variables is not used to locate an application. Subsequent arguments may either be specified explicitely on the commandline. Any argument that starts with an at (@) sign is taken to introduce a filename, which contains one argument per line. The textual file may contain long arguments and filenames. However, Unices still impose limits on the maximum length of a directory name, and the maximum length of a file name. These lengths are not checked, because pegasus-invoke is oblivious of the application (e.g. what argument is a filename, and what argument is a mere string resembling a filename). RETURN VALUE
The pegasus-invoke tool returns 127, if it was unable to find the application. It returns 126, if there was a problem parsing the file. All other exit status, including 126 and 127, come from the application. SEE ALSO
pegasus-kickstart(1) EXAMPLE
$ echo "/bin/date" > X $ echo "-Isec" >> X $ pegasus-invoke @X 2005-11-03T15:07:01-0600 Recursion is also possible. Please mind not to use circular inclusions. Also note how duplicating the initial at (@) sign will escape its meaning as inclusion symbol. $ cat test.3 This is test 3 $ cat test.2 /bin/echo @test.3 @@test.3 $ pegasus-invoke @test.2 This is test 3 @test.3 RESTRICTIONS
While the arguments themselves may contain files with arguments to parse, starting with an at (@) sign as before, the maximum recursion limit is 32 levels of inclusions. It is not possible (yet) to use stdin as source of inclusion. HISTORY
As you may have noticed, pegasus-invoke had the name invoke in previous incantations. We are slowly moving to the new name to avoid clashes in a larger OS installation setting. However, there is no pertinent need to change the internal name, too, as no name clashes are expected. AUTHORS
Mike Wilde <wilde at mcs dot anl dot gov> Jens-S. Vockler <voeckler at isi dot edu> Pegasus http://pegasus.isi.edu/ 05/24/2012 PEGASUS-INVOKE(1)

Check Out this Related Man Page

PEGASUS-DAX-VALIDA(1)													     PEGASUS-DAX-VALIDA(1)

NAME
pegasus-dax-validator - determines if a given DAX file is valid. SYNOPSIS
pegasus-dax-validator daxfile [verbose] DESCRIPTION
The pegasus-dax-validator is a simple application that determines, if a given DAX file is valid XML. For this, it parses the file with as many XML validity checks that the Apache Xerces XML parser framework supports. OPTIONS
daxfile The location of the file containing the DAX. verbose If any kind of second argument was specified, not limited to the string verbose, the verbose output mode is switched on. RETURN VALUE
If the DAX was parsed successfully, or only warning's were issued, the exit code is 0. Any 'error or fatal error will result in an exit code of 1. Additionally, a summary statistics with counts of warnings, errors, and fatal errors will be displayed. EXAMPLE
The following shows the parsing of a DAX file that uses the wrong kind of value for certain enumerations. The output shows the errors with the respective line number and column number of the input DAX file, so that one can find and fix them more easily. (The lines in the example were broken to fit the manpage format.) $ pegasus-dax-validator bd.dax ERROR in line 14, col 110: cvc-enumeration-valid: Value 'i386' is not facet-valid with respect to enumeration '[x86, x86_64, ppc, ppc_64, ia64, sparcv7, sparcv9, amd64]'. It must be a value from the enumeration. ERROR in line 14, col 110: cvc-attribute.3: The value 'i386' of attribute 'arch' on element 'executable' is not valid with respect to its type, 'ArchitectureType'. ERROR in line 14, col 110: cvc-enumeration-valid: Value 'darwin' is not facet-valid with respect to enumeration '[aix, sunos, linux, macosx, windows]'. It must be a value from the enumeration. ERROR in line 14, col 110: cvc-attribute.3: The value 'darwin' of attribute 'os' on element 'executable' is not valid with respect to its type, 'OSType'. 0 warnings, 4 errors, and 0 fatal errors detected. SEE ALSO
Apache Xerces-J http://xerces.apache.org/xerces2-j/ AUTHORS
Jens-S. Vockler <voeckler at isi dot edu> Pegasus Team http://pegasus.isi.edu/ 05/24/2012 PEGASUS-DAX-VALIDA(1)
Man Page