Signal handling is identical for pop3d,imapd,lmtpd afaik. They all share the same signalhandling code from
server.c and serverchild.c
SIGABRT is not handled explicitely by the code. No handler is installed. This could be os-specific. What are
you running on? I've never seen a kernel logline like your's with the kernel-path specified. But all I know is
linux...
Wolfram A. Kraushaar wrote:
In contrast to dbmail-imapd, a child process of dbmail-pop3d exits on
signal 6 (SIGABRT) if the client unexpectedly drops the connection.
Is this behavior intended?
syslog messages:
dbmail/pop3d[8151]: PerformChildTask(): incoming connection from [...]
/boot/kernel/kernel: pid 8151 (dbmail-pop3d), uid 65534: exited on signal
6
dbmail/pop3d[8151]: pop3_handle_connection(): error, uncomplete session
--
Wolfram
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
--
________________________________________________________________
Paul Stevens mailto:[EMAIL PROTECTED]
NET FACILITIES GROUP PGP: finger [EMAIL PROTECTED]
The Netherlands________________________________http://www.nfg.nl
