head	1.5;
access;
symbols;
locks
	nobody:1.5; strict;
comment	@# @;


1.5
date	99.05.21.18.51.17;	author nobody;	state Exp;
branches;
next	1.4;

1.4
date	99.05.12.18.42.28;	author nobody;	state Exp;
branches;
next	1.3;

1.3
date	99.05.12.18.42.17;	author nobody;	state Exp;
branches;
next	1.2;

1.2
date	99.05.12.18.41.54;	author nobody;	state Exp;
branches;
next	1.1;

1.1
date	99.05.12.18.41.50;	author nobody;	state Exp;
branches;
next	;


desc
@null
@


1.5
log
@null
@
text
@IDependOn-Set: 1
IDependOn-Set: 13
IDependOn-Set: 139
IDependOn-Set: 157
IDependOn-Set: 182
IDependOn-Set: 2
IDependOn-Set: 24
LastModifiedSecs: 926534548
Parent: 24
SequenceNumber: 2
Title: How do I kill Apache and the JVM as well when it is run from the command line?
Part: 0
Author-Set: jon@@working-dogs.com
HideAttributions: 1
LastModifiedSecs: 926534548
Type: monospaced
Lines: 35
----------
From: Pierpaolo Fumagalli <p_fumagalli@@fumagalli.org>
To: jon * <jon@@clearink.com>
Subject: Re: Failure to die: is it a bug?
Date: Wed, May 12, 1999, 11:38 AM

> > If you "control-C" the Apache process on Win32, it does not
> > kill the JVM.  Thus, if you think that - by merely stopping and
> > restarting Apache this way - you will get the JVM to reload,
> > you will eventually find out that you are in fact wrong.
> >
> > I was wondering if anyone else considers this an Apache bug?
> > I did not notice it filed in Apache bug database.
> 
> I have noticed this as well. I'm not sure that stopping Apache with
> control-c is the proper way to stop it though (I could be wrong so please
> correct me). If it is the proper way to stop it (I don't know the proper
> way), then it is a bug on our part. ;-( If it is not the proper way, then it
> is not a bug on our part. ;-)
> 
That's true... It's an Apache bug... When CTRL-C is pressed the
"shutdown" sequence cannot take place, and so, we cannot close the JVM.
The correct procedure for stopping Apache under windows is calling, from
another MS-DOS prompt window, apache -k shutdown. This kills the things
nicely.
Anyway this happens only when Apache is started manually from the
command line, and not when started as a service from the WindowsNT
control panel (but the command line operation is the only one permitted
under Windows95/98).

I worked a patch on it, against 1.3.0, I don't know if it still works...
I also asked to the new-httpd list, but I got no responses at all... I
merely don't know.....

        Pier
EndPart: 0
@


1.4
log
@null
@
text
@d5 1
@


1.3
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 926534537
d9 1
a9 1
SequenceNumber: 1
d11 42
@


1.2
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 926534510
d9 2
a10 2
SequenceNumber: 0
Title: New Item
@


1.1
log
@null
@
text
@d3 1
@
