On 01/20/10 13:33, Daniel wrote:
> Well I've restarted the director to get a critical job running, but as soon 
> as that job finishes I'll run a few more and show you what happens.  
> Essentially they show up as:
> 
> 
> Running Jobs:
> Console connected at 20-Jan-10 13:27
> JobId Level   Name                       Status
> ======================================================================
>    42         BackupServer1.2010-01-20_10.30.00_01 is waiting for execution
>    43         BackupServer2.2010-01-20_10.30.00_01 is waiting for execution
>    44         RestoreFiles.2010-01-20_12.20.31_03 is waiting for execution
> 
> That's a simulation of previous results.
> 
> When I cancel the jobs and they sit there and then I restart the director, I 
> do NOT see the cancelled jobs show up in the "Terminated Job" list.

Possibly silly question:  What are the applicable job-concurrency
settings set to?


-- 
  Phil Stracchino, CDK#2     DoD#299792458     ICBM: 43.5607, -71.355
  alaric AT caerllewys DOT net   alaric AT metrocast DOT net   phil AT 
co.ordinate DOT org
         Renaissance Man, Unix ronin, Perl hacker, Free Stater
                 It's not the years, it's the mileage.

------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users