http://bugzilla.spamassassin.org/show_bug.cgi?id=3625
------- Additional Comments From [EMAIL PROTECTED] 2004-08-31 13:43 ------- Subject: Re: sysklogd rpm install stopped spamd processing On Tue, Aug 31, 2004 at 12:43:34PM -0700, [EMAIL PROTECTED] wrote: > something's up -- because the spamd process is definitely catching SIGCHLD and > logging something in response. Without looking at the other ticket comments , I would imagine the child tries to log, it sigpipes and dies, that sends a sigchild to the parent, which then has a handler and goes from there. spamd parent expects that it'll only get a sigchld when a child dies, so it'll spawn a new child per sigchld that comes in. so it seems like what is happening is the child dies, the parent respawns, then the child dies again because it receives another sigpipe at startup, rinse lather repeat. unfortunately a fix may not be so straightforward. the children currently inherit the logging system from the parent (there was talk about changing this, but for 3.1, etc.) the reason for this is that the parent sets up the logging bit (including "out to file") before dropping any privilege, so a sighup has problems as would trying to reset it via sigpipe. I'm not sure of a clean way to solve this issue though. at minimum, the parent sigpipe handler could see it's logging via syslog() and close/open appropriately. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
