On Tue, 12 Feb 2008, le dahut wrote:
> Does this mean that the second job (the one with a higher priority number)
> will be "forgotten" ? or that it will be run once the first job has finished
> ?
It will be run after the first job is finished.
Does this mean that the second job (the one with a higher priority
number) will be "forgotten" ? or that it will be run once the first job
has finished ?
Alan Brown a écrit :
> On Fri, 8 Feb 2008, le dahut wrote:
>
>> I'll use priority, since both jobs must be based on the same schedule
>> inc
On Fri, 8 Feb 2008, le dahut wrote:
> I'll use priority, since both jobs must be based on the same schedule
> included file.
If you use differing priorities, only one job will run at a time.
-
This SF.net email is sponsore
Dan Langille a écrit :
> le dahut wrote:
>> Hello,
>>
>> I've a question about running 2 jobs at the same time.
>>
>> Here's my problem :
>> - a simple web interface lets users schedule a backup job
>> - this interface writes in "/etc/bacula/myschedule.conf" (which is
>> included in bacula-dir.c
le dahut wrote:
> Hello,
>
> I've a question about running 2 jobs at the same time.
>
> Here's my problem :
> - a simple web interface lets users schedule a backup job
> - this interface writes in "/etc/bacula/myschedule.conf" (which is
> included in bacula-dir.conf) and restarts bacula-dir
Ins
Hello,
I've a question about running 2 jobs at the same time.
Here's my problem :
- a simple web interface lets users schedule a backup job
- this interface writes in "/etc/bacula/myschedule.conf" (which is
included in bacula-dir.conf) and restarts bacula-dir
- 2 types of jobs are defined, Serve
