Re: ap_process_child_status() and child pid exit signal logging

Wed, 02 Dec 2009 07:03:33 -0800 

BEGIN:VCALENDAR
PRODID:Zimbra-Calendar-Provider
VERSION:2.0
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:Europe/Berlin
BEGIN:STANDARD
DTSTART:19710101T030000
TZOFFSETTO:+0100
TZOFFSETFROM:+0200
RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=10;BYDAY=-1SU
TZNAME:CET
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:19710101T020000
TZOFFSETTO:+0200
TZOFFSETFROM:+0100
RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=3;BYDAY=-1SU
TZNAME:CEST
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:0138c6af-1dd5-485d-8c9f-ad90747c34da
SUMMARY:Re: ap_process_child_status() and child pid exit signal logging
ATTENDEE;CN=Jeff Trawick;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRU
 E:mailto:[email protected]
ATTENDEE;CN=dev;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:
 [email protected]
ORGANIZER;CN="Igor Galić":mailto:[email protected]
DTSTART;TZID="Europe/Berlin":20091202T160000
DTEND;TZID="Europe/Berlin":20091202T170000
STATUS:CONFIRMED
CLASS:PUBLIC
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
TRANSP:OPAQUE
X-MICROSOFT-DISALLOW-COUNTER:TRUE
DTSTAMP:20091202T150303Z
SEQUENCE:0
DESCRIPTION:The following is a new meeting request:\n\nSubject: Re: ap_proce
 ss_child_status() and child pid exit signal logging \nOrganiser: \"Igor Gali
 ć\" <[email protected]> \n\nTime: Wednesday\, 2 December\, 2009\, 4:00:
 00 PM - 5:00:00 PM GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm /
  Vienna\n \nInvitees: \"Jeff Trawick\" <[email protected]>\; \"dev\" <d...@ht
 tpd.apache.org> \n\n*~*~*~*~*~*~*~*~*~*\n\nOn Wed\, Dec 2\, 2009 at 9:00 AM\
 , Kevin J Walters\n<[email protected]> wrote:\n>\n> Hi\,\n>\n>
  I've noticed that all versions of apache (1.3 to 2.2) will produce\n> error
  log output like this\,\n>\n> [Mon Jan  1 00:00:00 2009] [notice] child pid 
 12345 exit signal Segmentation fault (11)\n>\n> In the case of a segmentatio
 n fault or anything that produces a core\n> dump this is a relatively seriou
 s error but it's only marked at notice\n> level due to setting of APLOG_NOTI
 CE in the code.\n\nAPLOG_NOTICE is special:  Such messages cannot be suppres
 sed by any\nLogLevel setting.  I guess that is behind the choice of APLOG_NO
 TICE.\n\nThere's some inconsistency w.r.t. other log messages though.  Child
 \nprocess crashes aren't as serious as some other errors that use\nAPLOG_CRI
 T or APLOG_EMERG.  So why are those other error messages\nsuppressible?
X-ALT-DESC;FMTTYPE=text/html:<html><body><h3>The following is a new meeting 
 request:</h3>\n\n<p>\n<table border='0'>\n<tr><th align=left>Subject:</th><t
 d>Re: ap_process_child_status() and child pid exit signal logging </td></tr>
 \n<tr><th align=left>Organiser:</th><td>\"Igor Galić\" &lt\;i.ga...@brainswa
 re.org&gt\; </td></tr>\n</table>\n<p>\n<table border='0'>\n<tr><th align=lef
 t>Time:</th><td>Wednesday\, 2 December\, 2009\, 4:00:00 PM - 5:00:00 PM GMT 
 +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna\n </td></tr></t
 able>\n<p>\n<table border='0'>\n<tr><th align=left>Invitees:</th><td>\"Jeff 
 Trawick\" <[email protected]>\; \"dev\" <[email protected]> </td></tr></t
 able>\n<div>*~*~*~*~*~*~*~*~*~*</div><br>On Wed\, Dec 2\, 2009 at 9:00 AM\, 
 Kevin J Walters<br>&lt\;[email protected]&gt\; wrote:<br>&gt\;
 <br>&gt\; Hi\,<br>&gt\;<br>&gt\; I've noticed that all versions of apache (1
 .3 to 2.2) will produce<br>&gt\; error log output like this\,<br>&gt\;<br>&g
 t\; [Mon Jan  1 00:00:00 2009] [notice] child pid 12345 exit signal Segmenta
 tion fault (11)<br>&gt\;<br>&gt\; In the case of a segmentation fault or any
 thing that produces a core<br>&gt\; dump this is a relatively serious error 
 but it's only marked at notice<br>&gt\; level due to setting of APLOG_NOTICE
  in the code.<br><br>APLOG_NOTICE is special:  Such messages cannot be suppr
 essed by any<br>LogLevel setting.  I guess that is behind the choice of APLO
 G_NOTICE.<br><br>There's some inconsistency w.r.t. other log messages though
 .  Child<br>process crashes aren't as serious as some other errors that use<
 br>APLOG_CRIT or APLOG_EMERG.  So why are those other error messages<br>supp
 ressible?</body></html>
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER;RELATED=START:-PT5M
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR

Reply via email to