You might configure concurrent jobs as a solution. That way, if one client is off-line, it doesn't hold up the whole show for the other jobs. Otherwise, the jobs will queue and wait patiently for the device to become available.
Erich On Jan 3, 2007, at 11:38 AM, Chris Rodgers wrote: > Does anyone have any ideas what is causing bacula to jam up like this? > > I'm sorry if I have provided too much information, but I don't have > any > real idea which parts of the configuration/etc. may be to blame. > > Thanks, > > Chris. > > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
