Quoting Kern Sibbald <[EMAIL PROTECTED]>: > On Thursday 23 March 2006 20:35, Turbo Fredriksson wrote: >> Quoting "Dan Langille" <[EMAIL PROTECTED]>: >> > NOTE: any disabled jobs are renabled if you restart bacula-dir. >> >> That wasn't nice :) It can be, and probaby is in most cases but >> I'd still would want a way to permanently disable a client... How >> about a third option 'permanent'? > > If you want to permanently change it there is no choice but to add a: > > enabled = no > > to the Job resource in the .conf file.
Yes, but I can't do that through the database. That was the whole point... I want the possibility to disable a client via my SNMP interface, which only have access to the database... Besides, a change of the config file require a restart of the server to take affect, and it's very possible that such a thing (downtime, even for a short time) isn't desired. -- Why can't programmers tell the difference between halloween and christmas day? Because 25 DEC = 31 OCT. ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
