This is a major improvement. The only issue now is when we embed an image in the body of the message elog makes a nice thumbnail. When you move the message to another logbook the thumbnail doesn't work and instead it shows the MASSIVE full size version of the picture instead. Is that possible to fix?

Thanks Stefan!

Mike

Hi,

There's seems to be a memory leak with elogd.exe running windows.  I had this problem with older version of elogd.exe, i've just upgrade to the latest and the problems still exist. I've had this issue with earlier versions.  I've just upgrade elog to the latest 2.76 version. The memory leak still persist. I really appreciate if you or anyone here can help me resolve this issue.

Thank!

JH

> > > > elogd continues to run after a SIGHUP. If a second SIGHUP is received the daemon terminates.
> > > > This was observed on Solaris 10 (SPARC).
> > > > The documentation states that elogd should re-read configuration after receiving SIGHUP.
> > > 
> > > I tried to reproduce this but without success. I could send many SIGHUPs without the daemon terminating. Maybe 
> > > you modified the configuration file in between and elogd barked out because of some wrong configuration? Try to 
> > > start the daemon interactively and see what exactly happens if you send several SIGHUPs.
> > 
> > The problem is that under Solaris signal handlers installed via signal() get uninstalled *before* the signal handler
> > is called.  Thus the second time elogd receives a SIGHUP, you get the default action, which is to kill the process.
> > 
> > The solution is to use the POSIX sigaction() call instead of signal(). 
> 
> Can you try to modify the signal() calls into sigaction(). If this really works under Solaris, I will incorporate this 
> then into the distribution.

Here is the patch.  It works under both Solaris and Linux.

ELOG has been carefully designed not to contain memory leaks. The server for this forum for example runs for months without problem:

[ritt@midas ~]$ ps aux | grep elogd

elog      1958  0.4  3.1  39412 32940 ?        Ss   May09 178:16 /usr/local/sbin/elogd -D -c /usr/local/elog/elogd.cfg

So if you have a problem, it must be specific to your installation. You should note that if you up- or download big attachents, memory gets allocated for some network buffers to contain these attachments. The buffer is kept to contain the largest attachment, it will never shrink. But once established, it will also not grow. If you see however a constant increase in memory consumption, I would appreciate if you tell me how you do this. Like which configuration you use, if you just read entries or also upload them, etc. etc. Once I can reproduce exactly your problem, I can try to fix it. 

Can you try revision #2206? 

> Here is the patch.  It works under both Solaris and Linux.

Thanks! I put that into revision #2207.

 Stefan,

Works perfectly, thanks for the fix you rock!

Mike