John,
I think I had to create a bogus schedule, that bacula wouldn't accept
the job config without a schedule. I think I'll disable the job in bconsole
and try to start it remotely. Just see what happens...
-Shon
On Wed, Oct 6, 2010 at 2:30 PM, John Drescher <[email protected]> wrote:
> 2010/10/6 Mingus Dew <[email protected]>:
> > I am running Bacula 5.0.1 and have a question about Disabled Jobs.
> >
> > I have some jobs configured that do not have an active schedule (i.e.,
> > bacula never automatically queues or runs them)
> > Instead, these jobs are run by a remote user that logs into the backup
> > server and runs a script to run the configured job on demand.
> >
> > If I disable these jobs via console, will this prevent them from being
> run
> > by bconsole?
> >
>
> I believe disabling jobs via bconsole just temporarily disables any
> schedule for that job until you restart the director in which case the
> job returns to its normal schedule. Well that is how it has worked for
> me. I have been trying to kill a job for months, I keep doing it in
> bconsole only to forget to change the schedule only to have the job
> come back after I restart the director.. I know its easy to edit the
> file. I did not actually think about this or I would have solved it a
> long time ago with exactly what you did. I mean get rid of the
> schedule. Or was the problem I used the default job as a base. I am
> babbling sorry, too much coffee . end here.
>
> John
>
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
