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. |
No big deal - I looked at the code and you did a much more thorough job than I
would have done. Appreciate all of the hard work -- this product is masterful!
> Sorry for that. The idea is that the -4 is the minor number between releases
> (mainly for bug fixes and impatient users (;-) ). I accidently overwrote the
> -4 version several times when testing a new RPM building scheme, but I promise
> to take more care in the future (:-)))
>
> Having the CVS revision in the executable is however a good idea and I will
> put it in.
>
> > Stefan, would it be ok to add the "minor" revision level to the VERSION
> > constant? I've been doing this after I download source just so I can keep
> > things straight, you keep cranking out versions ;->
> >
> > EX:
> > #define VERSION "2.5.4-4"
> > BECOMES
> > #define VERSION "2.5.4-4-1.483" or something like that?
> >
> > Just a thought.
> >
> > Thanks |