You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@apr.apache.org by bu...@apache.org on 2006/10/01 22:50:08 UTC
DO NOT REPLY [Bug 40651] - SHELL_PATH in apr_arch_threadproc.h hangs Apache piped logger
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=40651>.
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=40651
rpluem@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
------- Additional Comments From rpluem@apache.org 2006-10-01 13:50 -------
(In reply to comment #0)
> I use Apache 2.2.3 on Solaris. All Logfiles are configured to use rotatelogs.
> Whenever I restart Apache either with "restart" or with "graceful" The first
> piped logger, which cares about the global error log, is left over in the
> process table. To be more precise: For all loggers new processes get started,
> and all apart from the described old one terminate. The problem is this
> unnecessary old process that doesn't die.
Some questions:
1. Does the respective /bin/sh -c die?
2. Does a new rotatelog process get forked after the restart?
3. What is the parent process of the hanging logrotate process
4. What version of Solaris do you use?
5. Could you please truss /bin/sh -c and logrotate during the restart with
options -faedl -vall -rall -wall?
> It would be nice to at least document the behaviour. Really nice would be to
> make SHELL_PATH changeable via configure and to be able to change it via Apaches
> configure (and if that would be documented).
Sounds reasonable to me.
--
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.