On Wed, Jan 25, 2006 at 03:52:46PM +0200, Eugene Filatov wrote: > I use small script which starts greylist again after crash. I don't know > how to start it automatically again under gdb. Another bad thing is that > sometimes greylist works well for two or three days, sometimes it crashes > twice per day. I think that keep gdb running on my server is not very good > thing for server's resources. I don't think it's such a problem. gdb will just sit down quitely until the kernel tells it that the traced process got a signal. What you need is a way to detect that the milter crashed. On my system (NetBSD), ps will report a traced and stoped program by a TX in the flags column. Maybe you can tweak your script so that it restarts milter-greylist when it sees an instance in that state? > > If it's not a limit issue, then it's a bug... > How can I catch it? Any ideas? We need to know where it happens, and a gdb backtrace will tell us that. -- Emmanuel Dreyfus manu@...
Message
Re: [milter-greylist] milter-greylist-2.0.2 crash
2006-01-25 by Emmanuel Dreyfus
Attachments
- No local attachments were found for this message.