On Thu, Jan 03, 2002 at 11:44:49AM -0500, Gary MacDougall wrote:
> Right, and I think its strange that the parent process felt the need
> to kill the child process. It might be justified if the child seg'd
> or died, but i thought xinetd handled this with more grace than say
> inetd... just curious, thats all.
No, no, xinetd didn't killed the proftpd process. It just started it, then
realized that it's child just died, and then saved the pid number and
duration time for debugging reasons in the syslog as it couldn't do more.
.... ProFTPD terminating (signal 11)
xinetd[17612]: EXIT: ftp status=1 pid=3425 duration=8(sec)
-christian-
--
Christian Hammers WESTEND GmbH - Aachen und Dueren Tel 0241/701333-0
[EMAIL PROTECTED] Internet & Security for Professionals Fax 0241/911879
WESTEND ist CISCO Systems Partner - Premium Certified
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
