Re: Embedded images break when moving from one book to another., posted by Mike on Thu Jun 4 17:51:02 2009
|
Stefan Ritt wrote:
|
Memory leak in 2.76 elogd.exe, posted by jon huang on Thu Jun 4 17:51:50 2009 
|
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 |
|
Re: elogd dies after receiving second SIGHUP, posted by Paul T. Keener on Thu Jun 4 18:49:29 2009
|
> > > > 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.
|
|
Re: Memory leak in 2.76 elogd.exe, posted by Stefan Ritt on Fri Jun 5 10:51:17 2009
|
jon huang wrote:
|
|
Re: Embedded images break when moving from one book to another., posted by Stefan Ritt on Fri Jun 5 12:42:55 2009
|
Mike wrote:
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 |
|
Re: elogd dies after receiving second SIGHUP, posted by Stefan Ritt on Fri Jun 5 13:18:00 2009
|
> Here is the patch. It works under both Solaris and Linux.
Thanks! I put that into revision #2207. |
|
Re: Embedded images break when moving from one book to another., posted by Mike on Fri Jun 5 14:13:52 2009
|
Stefan Ritt wrote:
|
|
(my) Firefox breaks Elog with this config file, posted by Michael Husbyn on Wed Jun 24 13:23:49 2009
|
Hi,
Did a fresh install on a Windows 2003 server (and tried it on my personal computer)
After startup I can click on Norway/nor, and then the server
just stops responding. I see in the log nothing, the last line: Received unknown cooke "style"
Then it stops responding and after a few seconds I see
the dos window returns to commandline prompt.
Probably a very bad config file.
On Windows XP it informs we of Dr Watson, memory could not be read |