> kill -HUP <pid>; sleep 2; kill <pid>
Thanks, I could reproduce the problem. It had to do that a SIGHUP aborts the select()
command, which some listen socket marked, so that elogd goes into an accept() call, waiting
there indefinitely (or until a new browser request arrives). I fixed that. New version
under CVS. |
When creating new logbooks, I will create a single entry to test the
configuration. After revising the configuration I want to delete that
single entry and create a new one based on the revised config.
elogd will crash every time upon deleting that single entry with an
xrealloc error. Here are the syslog entries leading up to the crash:
Oct 9 08:09:41 obstin8 elogd[20614]:
GET /Support/1?cmd=Delete&nextmsg=0&confirm=Yes HTTP/1.1^M Connection:
Keep-Alive^M User-Agent: Mozilla/5.0 (compatible; Konqueror/3.3; Linux)
(KHTML, like Gecko)^M Referer: http://localhost:8080/Support/1?cmd=Delete^M
Accept: text/html, image/jpeg, image/png, text/*, image/*, */*^M
Accept-Encoding: x-gzip, x-deflate, gzip, deflate^M Accept-Charset:
iso-8859-1, utf-8;q=0.5, *;q=0.5^M Accept-Language: en^M Host:
localhost:8080^M Cookie: urem=0; upwd=dDRubjNyBDI=; unm=mstolove
Oct 9 08:09:41 obstin8 elogd[20614]: xrealloc: not enough memory
This is on a Slackware 10 box using kernel 2.6.7. Elogd is accessed
directly, not through an Apache proxy. |