Package: samba
Version: 2.2.3a-14.2
Followup-For: Bug #302378
Hi,
3 Networks, 4 Machines, same Problem.
> I have no idea where the SIGHUPs came from
They came from logrotate:
/etc/logrotate.d/samba
--- cut ---
postrotate
killall -q -HUP smbd || true
--- cut ---
Log and gdb backtrace follow:
[2005/0
Package: samba
Version: 2.2.3a-14.2
Followup-For: Bug #302378
Hi,
it seems this is the same bug I'm encountering. Since the security
update, smbd occasionally exited with an internal error. Turning on
debugging revealed a preceding SIGHUP, and sure enough, sending smbd a
SIGHUP makes it segfault.
2 matches
Mail list logo