httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 41148] New: - no startup option to keep a foreground process
Date Mon, 11 Dec 2006 12:51:05 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=41148>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=41148

           Summary: no startup option to keep a foreground process
           Product: Apache httpd-2
           Version: 2.3-HEAD
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Core
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: lkcl@lkcl.net


a very important command-line startup option is missing:
the ability to send all logging to stdout/stderr plus having the
main process in foreground whilst all other child processes/threads
are running - in production mode.

the reason why this is important is because it is a standard way
to run daemons.

and - i am not kidding - apache is the _only_ major free software
service, out of fifty or so that i've come across - that do not have
this option.

there is a specific reason why i need this option: it's because of
depinit.  the use of depinit does away completely with the need for
stupid /var/run/*.pid files (it keeps an eye on the main process
and automatically restarts it if that main process dies),
and with the need for opening up separate log files (it can read
from stdout and stderr and send those to another service, for it
to process via optional filter programs and ultimately on to a
destination service e.g. syslogd)

in a few simple lines of c-code depinit replaces all the cruft that
is duplicated in every single service.

and apache is literally the _only_ major free software service that
cannot be 'managed' by depinit.

the reason why it cannot be managed by depinit is because apache forks
as a daemon, closing stdin-out-err etc. etc.  so, it has to be treated
as a 'legacy' service, and therefore any paralllel dependencies on 
apache cannot be properly managed.

also, depinit cannot give apache a chance to exit properly: it can only
run /etc/init.d/apache2 stop and leave it at that.  there's no chance to
find out if that succeeded or failed: after a few seconds, any remaining
processes are terminated with extreme prejudice.

if the option was added to run in foreground, in production mode, then
depinit could send signals to the main apache process to get it to shut
down gracefully, then wait until that main process exited.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message