On Fri, 11 Jul 2008, [EMAIL PROTECTED] wrote: > I just upgraded on of our MXs, and now I'm having a problem where > dkim-filter periodically dies. Doesn't dump core, doesn't log SEGV, > nothing.
SM suggested compiling with "-g" and running the filter that way, hopefully producing a coredump. Remember that these days you need to satisfy certain system requirements to get coredumps: - process has to have write permission to its current working directory - process to have no coredump size limit imposed (set this with the shell) - process must not have changed its userid (i.e. don't use "-u" on the command line or "UserID" in the configuration file), OR you must have configured your system to dump cores anyway You can also capture the message which caused it to die by running your sendmail MTA with the flag "-d71.100". When the filter crashes, any message(s) in progress will be quarantined and you can get them out of the queue manually. If the message doesn't reveal anything sensitive, you can (at your discretion of course) submit it as data about the problem. ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ dkim-milter-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
