On Fri, Oct 21, 2005 at 12:27:11PM +0300, Fredrik Nyberg DC wrote: > >>I see. That's a problem, because lot's of data is lost on exit. USR1 or > >>USR2 could be used, I guess. I wonder why libmilter is not returning to > >>main after it catches SIGTERM. atexit is not triggered correctly. > >We could trigger milter-greylist exit using a control socket, or using the > >MX sync socket... > How does this solve the problem that libmilter apparently catches > SIGTERM and does not return to main? > Or am I missing something? The goal is to remotely shut-down milter-greylist with a disk dump. You can do this by issuing a signal and catching it, but that is wrong because libmilter documentation says we should not catch signals. An alternative is to have a control socket, or to use the MX sync socket to get the shutdown command. -- Emmanuel Dreyfus manu@...
Message
Re: [milter-greylist] some strange behavior with mxsync
2005-10-21 by Emmanuel Dreyfus
Attachments
- No local attachments were found for this message.