On Sunday 27 November 2005 08:43, Ross Boylan wrote:
> On Fri, Nov 25, 2005 at 11:08:50PM +0100, Kern Sibbald wrote:
> ....
>
> > We might be able to do something like:
> >
> > skip job=Job-name
> >
> > which would skip the next scheduled time for Job-name
>
> Leaving aside the somewhat oddball and/or misremembered cases, will
> there ever be situations in which more than one scheduled job has the
> same job name? For example, if the job is scheduled to run frequently
> (e.g., less than every 2 hours?), could you get 2 entries for it on
> the schedule?
Yes.
>
> If the answer is yes, than probably some way to distinguish different
> jobs (in the sense of individual tasks) with the same job name would
> be needed.
Currently they are only distinguished when the job starts running and it is
attributed with a "Job", which is a unique job name, and a JobId, which is
not guaranteed to be unique (this may be a surprise to some of you, and it is
also the reason for the long weird looking unique job names printed in every
Job report).
--
Best regards,
Kern
(">
/\
V_V
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
