Aaron, I saw a way to repoduce the SIGALRM, when running the daemons under valgrind with the tracechildren option I mentioned in my submission (with dbmail.supp) you can connect to any of the daemons from the network and then just let the connection sit open till the OS cleans up the idle connection (I saw this from someone scanning my network a day or so ago.), this will send the signal SIGALRM to the daemon, as far as I can tell on my Linux FC2/ CentOS x86_64 4.2 machines. Or could you use kill -s SIGALRM <pid of -n running dameon> ?
Just my .02 -leif On Fri, February 24, 2006 6:44 pm, Aaron Stone wrote: > Oleg, Paul and I have started seeing weird segfaults in the daemons. > Possibly starting from about two weeks ago, although we're not totally > sure. I have some evidence (posted earlier this week) that it's in the > SIGALRM handler (maybe all signal handlers?), and that's what's causing > the "glib: corrupted double linked list" error messages. > > What we need now are some good trace logs, gdb logs, valgrind logs, to > help narrow down when things go crazy and what leads up to it. Time for > more eyeballs to make this bug shallow! > > DBMail 2.1.4 will be released as soon as we figure this out! > > > Aaron > > > > _______________________________________________ > Dbmail-dev mailing list > [email protected] > http://twister.fastxs.net/mailman/listinfo/dbmail-dev > >
