> Of course it is not running, that's what the whole story is about. I have a > bunch of desktop/laptop clients configured that can be shut > down/disconnected/not around at random and are well beyond my control. Sorry. I totally missed your point but I see now.
> I want > bacula to cease any further attempts to contact them after initial configured > FD timeout value expires. It appears that it is still trying to do something > after that, something that I don't even understand. And those stuck jobs > block the queue so no other scheduled jobs can run. I am not sure if this still exists in the latest bacula-2.2.0 as I have never messed with fd timeouts however at work (dozens of clients that may be off backed up every day) I combat this by allowing concurrency. John ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
