Re: Samba hogs syslogd and fails

On 2024-09-27 12:47, Andrea Venturoli wrote:
> On 9/27/24 12:38, Frank Leonhardt wrote:
> 
>> As no one else who knows better has answered...
>> ...
>> If you didn't know this already, I hope it helps.
> 
> Thanks.
> I had dealt with a similar problem long ago, so, more or less, I knew, 
> but a refresh was useful.
> 
> I fully understand that this will only delay the problem, not solve it.
> I guess "solving" it should be a Samba problem, not an OS one, unless 
> there's a way to force the syslog API to stop and wait when the buffers 
> are exahusted.
> 
> I'll try anyway to increase these values, but the real problem is 
> vfs_full_audit won't tell when this happen, so you have to know you 
> lost logs... and usually you don't :(

Here's a crazy idea. syslogd does a DNS lookup to log the originating 
hostname. Try running it with the -n option to disable this if it can't 
resolve your hostname - DNS timeouts are a bitch.

Would it be possible to clear the O_NONBLOCK flag on the syslog socket? 
I would have thought so but I'm not sure how (other than recompiling 
syslogd).

-- 
------
25-Sept-24 My apologies to everyone who I appear to have ignored for the 
last few years. A procmail script was misfiling some replies to 
Questions to the wrong folder.