Hi,

when the bacula services are (for whatever reason) terminated while there are 
still jobs in the queue, these jobs will reside as "zombies" in the Catalog. 
Unfortunately, the web interface Bweb will rely on Catalog entries for 
the "Running jobs" view.

How do you handle dead job entries in your databases, i.e. jobs that are in 
state "Created", "Running" or "Blocked", but are in fact no longer queued by 
the director?

Do you think I should come up with the topic in the -devel mailinglist? Maybe 
these jobs should be marked as "Canceled" by the director during shutdown, or 
during initialization?

Thx,
   Bastian

-- 
Collax GmbH . Burkheimer Straße 3 . 79111 Freiburg . Germany
p: +49 (0) 761-45684-24
f: +49 (0) 761-45684-10        www.collax.com

Geschäftsführer: William K. Hite / Boris Nalbach
AG München HRB 158898 . Ust.-IdNr: DE 814464942
\ "There is no spoon."

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