Re: webmin-0.990-1 spawns several processes and locks server

[Joe C. <jo...@sw...>]

This one is a weird issue, and one that I've seen quite a few times now, 
but haven't reproduced it lately myself (but I still have a client that 
can trigger it on his machine--while I cannot).

I was able to make it happen in the past with Netscape 6.0, but these 
days, neither Mozilla or current Netscape makes it happen for me. 
Another client /always/ has about 25 Webmin processes on his machine, 
and I don't know where they're coming from.  Darnedest thing I've seen 
in a while...

Jamie, would it be possible to get a forced timeout on child miniserv.pl 
processes if they don't do something for some number of minutes?  It is 
just a simple 'process per connection' server, isn't it?  I know that 
webmin spawning processes that don't end can cause it to hang around, 
but if after 5 minutes something hasn't returned, the browser has 
probably timed out the request already anyway.  So no use waiting for a 
long process if there will be no one around to see it finish.  Just a 
thought.

Andrew Kornak wrote:
> I apologize, I should have mentioned that I have used webmin with
> IE and tried Netscape 7 now to verify it wasn't a browser issue. I will
> try other browsers if you think it is still a browser issue. But, I
> personally
> don't believe it's a browser issue.
> 
> -Andrew
> ----- Original Message -----
> From: "Andrew Kornak" <ak...@ra...>
> To: <web...@li...>
> Sent: Tuesday, September 10, 2002 9:11 PM
> Subject: Re: webmin-0.990-1 spawns several processes and locks server
> 
> 
> 
>>I just tried it with netscape 7.0 and the same thing happened.
>>Server almost died before I killed the browser and stopped webmin.
>>
>>-Andrew
>>----- Original Message -----
>>From: "Jamie Cameron" <jca...@we...>
>>To: <web...@li...>
>>Sent: Tuesday, September 10, 2002 8:33 PM
>>Subject: Re: webmin-0.990-1 spawns several processes and locks server
>>
>>
>>
>>>You aren't the first person to report this, but I have been unable to
>>>re-produce it on my own systems in order to solve it. I suspect it may
>>>be triggered by certain browsers .. which browser are you using, and
>>
> does
> 
>>>it still happen if you try a different one?


-- 
Joe Cooper <jo...@sw...>
Web caching appliances and support.
http://www.swelltech.com