Bastian Friedrich-2 wrote:
> 
> Hi,
> 
> On Tuesday 17 June 2008, ebollengier wrote:
>> The most simple is to remove them with bconsole
>> delete jobid=1,2,3,4,5
> 
> I'd regard that being a task of the system, not a manual thing.
> 

"delete jobid=" does more than just a delete a Job record, it
cleanups jobmedia, file table, logs, etc...

To be automatic, we can use something like

SELECT 'delete jobid=' || JobId FROM Job WHERE JobStatus IN ('C','R','B');


Bastian Friedrich-2 wrote:
> 
> 
> I am considering doing an "update jobs set Status='A' where Status in 
> ('C','R','B')" in my init script; on the other hand: why does Bacula not
> do 
> that itself? The Director should be responsible for maintaining consistent 
> data in the catalog. :)
> 

If you want to keep them in Error, your idea can work, but be sure that the
director is not running :)

The director doesn't cleanup old jobs at start, i will put that on my TODO
list.

Bye

-- 
View this message in context: 
http://www.nabble.com/Dead-jobs%2C-esp.-in-Bweb-tp17864183p17960876.html
Sent from the Bacula - Users mailing list archive at Nabble.com.


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users