Hello,
Those of you who read the beta3 release notes with care will remark that I
have changed the somewhat contested jobuid command line keyword to ujobid
(unique job id). Hopefully this will avoid any confusion that could arise.
In summary, the command line keywords permitted on a number of commands (e.g.
list) are:
keyword meaning
jobid the numeric (non-unique) jobid of a Job
ujobid the unique jobid
job the name of the job resource (from Name =)
jobname same as the above -- job resource name
Example:
list jobid=1
lists a summary of Job with id 1 if any
list ujobid=kernsave.2006-02-25_12.38.07
lists a summary of Job kernsave.2006-02-25_12.38.07, which on my current
test environment is the same as jobid 1.
list job=kernsave
lists a summary all jobs named kernsave.
list jobname=kernsave
same as above
Best regards, Kern
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
