Daniel De Marco wrote:
> * Dan Langille <dan AT langille DOT org> [01/13/2010 20:03]:
>> I think you need to read up on 'concurrent jobs'.
>> "If you want to run concurrent jobs you should keep these points in mind:
>>      * See Running Concurrent Jobs on how to setup concurrent jobs.
>>      * Bacula concurrently runs jobs of only one priority at a time. It 
>> will not simultaneously run a priority 1 and a priority 2 job. "
> 
> I see, I tought that since the first job was stuck it wouldn't block the
> queue and the above would not apply, but thinking about it, it makes sense. 
> 
> So it is not possible to have a workaround or a different configuration
> so that a stuck job would not block the queue??

*cough*

I'm pretty sure you answered your own question.

------------------------------------------------------------------------------
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