Embedded images break when moving from one book to another., posted by Mike on Fri May 8 16:32:03 2009
|
Here's the issue. We use elog to develope products we need to be able to see all the thumbnail images in a
particular logbook. Our default view is to use the threaded view fully expanded in order to have all the thumbnails
be displayed for each product. This works fine but when we move one message to another logbook the thumbnails |
Re: Embedded images break when moving from one book to another., posted by Stefan Ritt on Thu Jun 4 15:37:44 2009
|
Mike wrote:
|
|
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:
|
|
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: Embedded images break when moving from one book to another., posted by Mike on Fri Jun 5 14:13:52 2009
|
Stefan Ritt wrote:
|
|
elogd dies after receiving second SIGHUP, posted by Kester Habermann on Tue Nov 11 16:45:04 2008
|
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: elogd dies after receiving second SIGHUP, posted by Stefan Ritt on Mon Nov 17 10:27:23 2008
|
> 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: elogd dies after receiving second SIGHUP, posted by Paul T. Keener on Wed Jun 3 19:53:13 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: elogd dies after receiving second SIGHUP, posted by Stefan Ritt on Thu Jun 4 09:49:13 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: 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: 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. |
Moving entry (and replies) from one log book to another, posted by David Pilgram on Fri May 1 14:01:44 2009
|
Hi Stefan,
When Moving entry (and replies) from one log book to another, is it possible to prevent elog from renumbering
|
|
Re: Moving entry (and replies) from one log book to another, posted by David Pilgram on Thu Jun 4 15:21:23 2009
|
Hi Stefan,
Any possibility on this one?
|
|
Re: Moving entry (and replies) from one log book to another, posted by Stefan Ritt on Fri Jun 5 11:29:43 2009
|
> Hi Stefan,
>
> When Moving entry (and replies) from one log book to another, is it possible to prevent elog from renumbering
|
Re: Moving entry (and replies) from one log book to another, posted by David Pilgram on Fri Jun 5 12:02:45 2009
|
Thanks Stefan, Downloading shortly and I'll let you know ;-)
> > Hi Stefan,
> >
|
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: Memory leak in 2.76 elogd.exe, posted by Stefan Ritt on Fri Jun 5 10:51:17 2009
|
jon huang wrote:
|
|
help with substituting subjects, posted by Alexander Withers on Wed May 6 20:49:24 2009
|
I am trying to add additional information to the subject of new entries:
Subst subject = $subject [INCIDENT $message id]
Subst on reply subject = Re: $subject
Fixed Attributes Reply = Subject
However,
the new entry subject looks like: |
|
Re: help with substituting subjects, posted by Stefan Ritt on Thu Jun 4 14:44:11 2009
|
Alexander Withers wrote:
|
|
User can modify Fixed Attributes Edit when selecting preview, posted by Allen on Thu May 7 15:09:09 2009
|
Hi. I'm pretty new to ELOG, so I'm not sure if I'm doing something wrong.
I have a bunch of fields set so that after an entry has been submitted, they cannot edit certain fields. When I click the edit button, everything |
|
Re: User can modify Fixed Attributes Edit when selecting preview, posted by Stefan Ritt on Thu Jun 4 14:37:54 2009
|
Allen wrote:
|
E-log crash, posted by soren poulsen on Thu May 14 17:41:44 2009
|
Hi
I am having a little problem with e-log that I can easily reproduce.
I have defined a number of constraints on my e-log fields and I am testing what happens when the user does not respect them. |
|
Re: E-log crash, posted by Stefan Ritt on Thu May 14 17:59:04 2009
|
soren poulsen wrote:
|
|
Re: E-log crash, posted by soren poulsen on Tue May 19 15:19:16 2009
|
Stefan
Ritt wrote:
|
|
Re: E-log crash, posted by Stefan Ritt on Thu Jun 4 14:05:58 2009
|
soren poulsen wrote:
|
|
Supress Email to Author of a message?, posted by Mike on Fri May 22 00:22:07 2009
|
I couldn't find an obvious solution to the problem. I'd like to suppress email
notification to the author of a message. I've had some people complaining
that when they use elog they don't want to get an email about what they wrote |
|
Re: Supress Email to Author of a message?, posted by Stefan Ritt on Thu Jun 4 14:04:21 2009
|
Mike wrote:
|