www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cott Lang <c...@internetstaff.com>
Subject mod_jserv/4743: kill -USR1 httpd restarts JVM
Date Tue, 20 Jul 1999 14:48:40 GMT

>Number:         4743
>Category:       mod_jserv
>Synopsis:       kill -USR1 httpd restarts JVM
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    jserv
>State:          open
>Class:          change-request
>Submitter-Id:   apache
>Arrival-Date:   Tue Jul 20 07:50:00 PDT 1999
>Originator:     cott@internetstaff.com
>Release:        1.3.6/1.0
Since Apache can/will restart with -HUP or -USR1, and -USR1 is supposed to
cause a graceful restart, can -USR1 *NOT* restart Jserv?   In particular,
it's common practice to do manual log rotations followed by a kill -USR1
to cause apache to reopen the log files - however, this isn't a good idea
on an apache running Jserv as JServ is dropped dead in it's tracks and
Easily :)
I'm not sure of the ramifications of making Jserv not cleanup on -USR1. I
know mod_perl does NOT reload perl scripts unless you enable a configuration
option to force it to do so. Can we get a config option for jserv to force
it to keep Jserv running after a kill -USR1 ?
[In order for any reply to be added to the PR database, you need]
[to include <apbugs@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]

View raw message