Let's think about effort versus reward:
1. Fix to include the FD in question in the log : 5 minutes to write,
perhaps even less.
2. Change the logging on every system
-AND-
Every time I see this error, send a message out to every team
with servers to administer and ask them if they see this message in
their local log.
Hm. That's 2-4 hours of work every time I see it. That's *EACH TIME*.
Can you understand why I can't take this seriously as a fix?
On Aug 2, 2006, at 4:18 AM, R.I. Pienaar wrote:
> it's not optimal but you can get each FD to write a log on its own box
> by adding an append directive to its messages settings.
>
> On 02/08/06, Alan Brown <[EMAIL PROTECTED]> wrote:
>> On Wed, 2 Aug 2006, Kern Sibbald wrote:
>>
>>>> Kern, is this fixed in a newer version?
>>>
>>> I believe more information is printed in 1.39.x, but there are so
>>> many changes
>>> that I cannot remember the exact case that was enhanced.
>>>
>>>> Can we get it fixed?
>>>
>>> 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.
>>
>> 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.
>>
>> 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.
>>
>> AB
>>
>>
>> ---------------------------------------------------------------------
>> ----
>> 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
>>
>
>
> --
> R.I.Pienaar http://www.devco.net
>
> ----------------------------------------------------------------------
> ---
> 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
--
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
