Hi list, Did someone experienced the same behaviour ? milter-greylist running fine for a while, updates done to greylist.conf and then process killed after some memory access: May 27 18:14:28 sulfateuse milter-greylist: reloading "/usr/local/etc/mail/greylist.conf" May 27 18:14:28 sulfateuse sm-mta[68434]: i4RGENbH068434: milter_read(greylist): cmd read returned 0, expecting 5 May 27 18:14:28 sulfateuse sm-mta[68434]: i4RGENbH068434: Milter (greylist): to error state May 27 18:22:20 sulfateuse sm-mta[68724]: i4RGMJQe068724: Milter (greylist): error connecting to filter: Connection refused by /var/milter-greylist/milter-greylist.sock May 27 18:14:28 blackbox /kernel: pid 66307 (milter-greylist), uid 25: exited on signal 11 Context: FreeBSD 4.10-RC3, milter-greylist 1.2.2 running into a jail. I have no core, perhaps it is due to the jail (to be checked). I'll try to reproduce this behaviour in order to get a core.
Message
SIGSEV upon conf reload
2004-05-27 by Cyril Guibourg
Attachments
- No local attachments were found for this message.