Hello Aviram
First, you'd better use proftpd ... less bugs :)
Anyway, in my proftpd there's a way to set the maximum idle time, so after
X minutes it'll close itself automatticly. probably in wuftpd too.
About the cpu, I have no idea.
Cya,
Oren.
On Mon, 12 Mar 2001, Aviram Jenik wrote:
> There's a problem that's been driving us crazy for a while here.
>
> One of our users connects using explorer as an FTP client. I'm not sure
> whether or not Explorer does an explicit disconnect when the window is
> closed, but in any case, after the FTP session is done, the process in.ftpd
> remains 'alive' until it's killed manually.
> It can even continue to 'run' for days, even though the FTP client is long
> gone. What's worse, it takes 100% CPU, and if a second connection is
> initiated, a second process remains with an additional 100% CPU (and this
> really takes the fun out of our 2 CPU machine).
>
> The whole thing is very strange, since there's no problem with any FTP
> clients besides this one, and there's nothing special about our FTP daemon
> (wu-ftpd-2.6.0).
> Does anybody have a clue about what might be causing this?
>
> - Aviram
>
>
>
>
> =================================================================
> To unsubscribe, send mail to [EMAIL PROTECTED] with
> the word "unsubscribe" in the message body, e.g., run the command
> echo unsubscribe | mail [EMAIL PROTECTED]
>
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
