[RHEL4.6] piped-log process set with ErrorLog directive in httpd.conf does not restart if it crashes.
Issue
- piped-log process, which is set with ErrorLog directive in httpd.conf, does not restart when it crashes.
- There is the following description about piped-log process of httpd.
http://httpd.apache.org/docs/2.0/en/logs.html#piped --------------------------------------------------------------- Apache will start the piped-log process when the server starts, and will restart it if it crashes while the server is running. --------------------------------------------------------------- - However, we confirmed the following behavior on our test environment.
- When piped-log process is set with ErrorLog directive, it does not restart when it crashes.
- When piped-log process is set with CustomLog directive, it restarts when it crashes.
- According to the above description, it seems this actual behavior is not expected one but is this correct hehavior?
- If so, please let me know the reason?
Environment
- Red Hat Enterprise Linux 4.6
- httpd-2.0.52-41.ent.7
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.