wwwoffle-win32  

Re: [WWWOFFLE-Win32] wwwoffle hangs, killing

Andrew M. Bishop
Fri, 18 Oct 2002 01:01:37 -0700

Jan Tisje <[EMAIL PROTECTED]> writes:

> for a long time I wondered HOW to kill a dead wwwoffle on w2k.
> Even superuser may not kill it via taskmananger, because it's a 
> service. From service management it can not be killed, because you 
> can only issue a "please end yourself". 
> 
> But now I realized that cygrunsrv is more mighty. Don't ask why. 
> 
> a cygrunsrv -E or cygrunsrv -S helps. 

> some threads already realized the server was not reachable. Others 
> hung and used 100% cpu.
> 
>       wwwoffled[736] Important: Exit signalled - waiting for 4 
>       child wwwoffles servers.

The main process exits, but does not kill the other processes.  It
waits for them to exit, which they should do after a timeout.

> cygrunsrv sends EXIT. 
> but it does not help. Perhaps some tasks end, some not. 
> Strangely I COULD kill one of the tasks using taskmanager. 
> 
>       wwwoffles[996] Warning: Unknown host 'c-evo.org' for server 
>       [Name Lookup Authoritative Answer Host not found].
>       wwwoffles[996] Warning: Cannot open the HTTP connection to 
>       c-evo.org port 80; [Name Lookup Authoritative Answer Host 
>       not found].
> [...]
>       wwwoffled[736] Important: Exiting.
> Finally after hanging up. 

> Could the main wwwoffle thread use a KILL after waiting some time? 

There shouldn't really ever be a reason to kill processes.  It
indicates a problem with WWWOFFLE.  As such I don't plan to add any
killing function into WWWOFFLE to kill the other processes, I would
prefer to try and fix the cause of the problem.

> Or could wwwoffle cut the tcp connections? 

It is not possible to cut the TCP connections.

> Shouldn't cygrunsrv get the exit signal from service management 
> and send it to wwwoffle? 

I would have thought so.

> Yesterday wwwoffle crashed similar... on the same host. But 
> yesterday this host was up. perhaps there is a problem with c-
> evo.org. 

I think that this is the most likely problem.

> System: win2k pro sp3, last cygwin update 1.10.2002

Have you seen the new cygwin library release from 13/10/2002?  It
looks like it has some good improvements for socket functions.

-- 
Andrew.
----------------------------------------------------------------------
Andrew M. Bishop                             [EMAIL PROTECTED]
                                      http://www.gedanken.demon.co.uk/

WWWOFFLE users page:
        http://www.gedanken.demon.co.uk/wwwoffle/version-2.7/user.html