[syslog-ng] One destination stopped logging?

[Balazs Scheidler]

On Mon, 2007-07-02 at 12:16 +0100, Hari Sekhon wrote:
> Yes I appreciate that you need debug info, but like I said it started 
> working again after I restarted syslog-ng so there isn't really any 
> opportunity for me strace the actual problem.
> 
> I know about getting logs from chroots, but this service is not 
> chrooted, it should use the same logging socket as everything else.
> 
> Is it possible that one blocked destination could affect another, last I 
> heard from you on this was that each destination was a separate line and 
> if one blocked it would only block that one destination, ie each 
> destination is independent, is that right?

I don't really remember the context where I said that. Destinations are
really somewhat independent (they use a different transport state), but
otherwise I never saw one destination to stall while all the others
work.

> 
> If I can make this error reproducable then I'll try to get you some 
> straces etc. and possibly a core dump.

thanks.

-- 
Bazsi