Raul Dias wrote:
> On Mon, 2005-12-19 at 21:12 +0100, manu@... wrote:
>>Raul Dias <raul@...> wrote:
>>
>>>How do we make to have mg to dump the memory DB?
>>It does it on its own every 10 minutes. It's true it could be useful to
>>have a way of dumping on purpose.
>>
>
> Yep, specially if you need to stop it (e.g. restart host, upgrade,
> testing).
>
> Raul Dias
>
>
I havent done any signal handling in my own programs but there are some
lines in the code which make me think milter-greylist should dump it's db.
--------- milter-greylist.c --------------
.
.
.
int
main(argc, argv)
.
.
.
/*
* Install an atexit() callback to perform
* a dump when milter-greylist exits.
*/
if (atexit(*final_dump) != 0) {
syslog(LOG_ERR, "atexit() failed: %s", strerror(errno));
exit(EX_OSERR);
}
.
.
.
--------------------------------------------
I did not see the errormessage so milter-greylist should have Installed
the atexit funktion.
After SIGTERM the program should execute exit() by default, but there
where no syslog entries form final_dump so it did not get called.
--
--------------------------------------------------------------------------------
M.Menge Tel.: (49) 7071/29-70316
Universitaet Tuebingen Fax.: (49) 7071/29-5912
Zentrum fuer Datenverarbeitung mail: menge@...-tuebingen.de
Waechterstrasse 76
72074 TuebingenMessage
Re: [milter-greylist] dump greylist.db on SIGTERM
2005-12-20 by Michael Menge
Attachments
- No local attachments were found for this message.