general/6476: apachectl restart hangs when using cronolog

[Jacques WERNERT <jw...@rush2win.com>]

>Number:         6476
>Category:       general
>Synopsis:       apachectl restart hangs when using cronolog
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon Aug 28 08:50:01 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     jwernert@rush2win.com
>Release:        1.3.12
>Organization:
apache
>Environment:
Solaris 7 (64)
>Description:
Hello,

I'm using cronolog has described in your FAQ but when I'm trying to re-read my configuration files using apachectl restart, the father of all httpd is waiting for the cronolog sub-processes to finish. I have to kill them by hand and then all is going ok. As I have a lot of virtual hosts so a lot of cronolog processes, it's quite boring.

Is there a workaround ?

Thanx for any help

Regards
>How-To-Repeat:
yes. Each apachectl restart does the same
>Fix:
Just have to kill any cronolog
>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <ap...@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!     ]