>>> Can we get it fixed? > On Wed, 2 Aug 2006, Kern Sibbald wrote: >> If it isn't already fixed, then it will be some time unless >> someone sends a >> patch since it is not on the top of my priority list which is >> already too >> long. Generally one knows exactly which daemon you are dealing >> with from the >> context unless you are driving the console with a script.
On Aug 2, 2006, at 3:42 AM, Alan Brown wrote: > In the case of mismatched file daemons it's easy enough to work out > which > one is playing up by running "status client" on each one. Nope. No configuration changes since I got that message, and no repeats of the message. "status client" worked on every one of them. > In other cases (spooling/unspooling or client unreachable, etc) run > out of > schedules then more information about which client has trouble and > which > job has just started spooling/unspooling would be useful. Yes. And given the number of different scenarios that this message could be generated for, I think that it's crucial. -- Jo Rhett senior geek Silicon Valley Colocation ------------------------------------------------------------------------- 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
