From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.16 i686)

Description of problem:
From time to time, one or more Apache child processes 'forget' the local
timezone and use GMT, causing related logging and CGI problems;
an extract from /var/log/httpd/access_log, showing correct asnd incorrect
entries:
 10.5.16.61 - - [17/Dec/2001:09:48:28 +1030] "GET
/faxbhtml/images/group.gif HTTP/1.0" 200 1293
10.5.16.61 - - [16/Dec/2001:23:18:28 +0000] "GET
/faxb/queue.cgi?list=all&all=1 HTTP/1.0" 200 45000
10.5.16.61 - - [17/Dec/2001:09:48:28 +1030] "GET
/faxbhtml/images/failed.gif HTTP/1.0" 200 1052
10.5.16.61 - - [16/Dec/2001:23:18:37 +0000] "GET
/faxb/queue.cgi?list=pending&all=1 HTTP/1.0" 200 5515
10.5.16.61 - - [17/Dec/2001:09:48:40 +1030] "POST /faxb/menu.cgi HTTP/1.0"
200 3573
10.5.16.61 - - [16/Dec/2001:23:18:40 +0000] "GET
/faxbhtml/images/submenu_userlist.png HTTP/1.0" 200 215
10.5.16.61 - - [17/Dec/2001:09:48:40 +1030] "GET /faxb/usermaint.cgi
HTTP/1.0" 200 6025
10.5.16.61 - - [17/Dec/2001:09:48:40 +1030] "GET
/faxbhtml/images/menu_custman_open.png HTTP/1.0" 200 366
10.5.16.61 - - [16/Dec/2001:23:18:40 +0000] "GET
/faxbhtml/images/button_adduser.png HTTP/1.0" 200 244
10.5.16.61 - - [17/Dec/2001:09:48:40 +1030] "GET
/faxbhtml/images/button_deluser

Our tests indicate that it is a problem with the child process - all
requests to affected children get the wrong localtime, reloading 
may fix the problem (depending on whether new children show the bug).



Version-Release number of selected component (if applicable):


How reproducible:
Sometimes

Steps to Reproduce:
1. Restart Apache.
2. Send enough requests to exercise all children;
3. Check TZ on timestamps in access log; goto 1 if necessary
	

Actual Results:  Sometimes, children report the wrong local time; the UTC
is correct, but they apply a timezone offset of 0 in place of whatever is
configured.

Expected Results:  They should show the correect local time, and agree
withb the parent process.

Additional info:

Also running mod_perl-1.21-10, but the problem occurs sporadically for both
mod_perl and regular requests; other servers running the same Apache but
different mod_perl versions show the same behaviour.