On Mon, Mar 12, 2001, Aviram Jenik wrote about "FTP hangs, taking 100% CPU":
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 additiona
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
On Tue, Mar 13, 2001, Yaron Zabary wrote about "Re: FTP hangs, taking 100% CPU":
3. Upgrade your ftpd.
You can try it (and you SHOULD do it because of the security holes in
the unpatched version 2.6.0!), but as I said 2.6.1(2) still gives me a
problem which appears similar, so maybe
On Mon, Mar 12, 2001 at 11:29:57PM +0200, 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
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
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:
