This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Suiqd as service [was: Re: New on sources: cygrunsrv-0.92]


On Thu, May 17, 2001 at 07:06:40PM +0200, Gerrit P. Haase wrote:
> system to access them. Thats it (with squid), but it works not with 
> Apache. 
> 
> There is NO error message in sys/event log.
> Only two messages:
> 
> 1:
> Cygwin Apache : Win32 Process Id = 0xFE : Cygwin Process Id = 0xFE :
>  `Cygwin Apache' service started.
> 
> 2:
> Cygwin Apache : Win32 Process Id = 0xFE : Cygwin Process Id = 0xFE :
>  `Cygwin Apache' service stopped.
> 
> No error...
>
> However, httpd is running.

Which probably means that apache has forked a daemon.

> You also wrote, it couldn't be killed, if a daemon forks and the parent
> dies, but that is not absolutely correct. Cygrunsrv is listed as a task
> and cygrunsrv could be killed, so the process it invokes dies, too.

? You're mixing two different things. Either the application forks/exits
and cygrunsrv behaves as above. In that case there's no cygrunsrv process.
Or the child app doesn't fork and you should not kill cygrunsrv but send
a stop message by calling `cygrunsrv -E <svcname>' or `net stop <svcname>'.
In that case, cygrunsrv sends a SIGTERM to it's child application to
give it a chance to close it's service gracefully. Killing cygrunsrv
is somewhat violent.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]