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: |
| 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 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
|
Can you try revision #2206?
|
Stefan,
Works perfectly, thanks for the fix you rock!
Mike |
|
Re: I can not access the Logbook from another machine, posted by Stefan Ritt on Mon Jun 8 07:34:18 2009
|
| Gerardo Pruneda wrote: |
|
I need some guidedance on how to access the logbook from another computer. I installed the logbook on a Windows server machine and started the logbook using port 81.
I can connect to the logbook on the same machine, but I can not access it from another machine on the same network.
I already confirm that the windows firewall is not enable.
|
Are your sure about the firewall, because this is the usual reason for that problem. Can you "ping" your server machine from the other machine (like "ping <server>"), maybe you have some network problems. |
|
Re: Move to: elog crashes with large no of entries being moved., posted by Stefan Ritt on Wed Jun 10 14:09:04 2009
|
> Hi Stefan,
>
> I've been slowly moving threads, and twice now so far (and reproducably) had elog crash.
>
> In each case, it is trying to move a thread with more than 24 entries; it copies the first 24 entries, then
> crashes with "Segmentation Fault". It does not erase the lock file /var/run/elog.pid
>
> I have got around this by manually copying the entries beyond no 24, then deleting the thread entry by entry.
>
> I am aware that I have an old and limited machine (586, 256MB RAM, running Slack 10), and at first I was
> "content" to write it off as that; but when it crashed for the second time at exactly the same entry (the
> twenty-forth) even though the size of the entries would have been significantly different, I wondered if there
> was some factor within elog that could affect this.
>
> I've not tried it with Copy to:, but imagine it will also be affected as the only difference with this and Move
> to: is the deletion of the thread after all the entries had been copied.
This rings a bell: it's probably related to some internal stack overflow, since the entries are copied
recursively. I have an idea on how to fix that, but I need time for that. |
|
Re: Move to: elog crashes with large no of entries being moved., posted by David Pilgram on Wed Jun 10 15:31:13 2009
|
> > Hi Stefan,
> >
> > I've been slowly moving threads, and twice now so far (and reproducably) had elog crash.
> >
> > In each case, it is trying to move a thread with more than 24 entries; it copies the first 24 entries, then
> > crashes with "Segmentation Fault". It does not erase the lock file /var/run/elog.pid
> >
> > I have got around this by manually copying the entries beyond no 24, then deleting the thread entry by entry.
> >
> > I am aware that I have an old and limited machine (586, 256MB RAM, running Slack 10), and at first I was
> > "content" to write it off as that; but when it crashed for the second time at exactly the same entry (the
> > twenty-forth) even though the size of the entries would have been significantly different, I wondered if there
> > was some factor within elog that could affect this.
> >
> > I've not tried it with Copy to:, but imagine it will also be affected as the only difference with this and Move
> > to: is the deletion of the thread after all the entries had been copied.
>
> This rings a bell: it's probably related to some internal stack overflow, since the entries are copied
> recursively. I have an idea on how to fix that, but I need time for that.
Thanks Stefan, I'll be keeping an eye out on any annoucement about this one! |
Re: wrapping long lines in config file, posted by Stefan Ritt on Mon Jun 15 12:51:27 2009 
|
| W.Koster wrote: |
Greetings,
I was wondering, is it possible to wrap lines in the config file ?
I have to add a dropdown lost which is kinda long and typing everything on one line will make ik kinda unreadable.
Somehow wrapping the line so each entry will get on a separate line would make it much better readable. (which
makes less errors).
|
What I do is to use an editor with automatic wrapping functions, like the free PSPad editor. It nicely wraps line and indicates that:
 |
|
Re: search and datetime, posted by Stefan Ritt on Mon Jun 15 12:56:32 2009
|
| Arno Teunisse wrote: |
|
Hello
I have the following in elog.cfg :
Attributes = Author, Author Email, Category, Customer, server, Subject , Change Window Begin , Change Window End
List display = ID,Author, Author Email, Category, Customer, server, Subject , Change Window Begin , Change Window End
Type Change Window Begin = datetime
Type Change Window End = datetime
So I want to be able to give a start and end date to the user. However : If I open a find/Search I see this :
There are for each Change Window <item> we get Start: and End: time entries. Was expecting only one date entrie .
Why is this ? Seems to be a feature of datetime or am i missing something.
|
Right, that's a feature. Many people want to specify a range when doing a query on a date. Like Change Window Begin after Jan 1st, 2009 and before Jan 5th, 2009. If you just want a single date, set both Start: and End: to the same date, or actually the End: to Start+1 Day to cover all 24 hours of the Start: date. Otherwise when you have data + time, you would have to match the exact second to retrieve a certain entry. So having a range there is more powerful. |
|
Re: wrapping long lines in config file, posted by W.Koster on Mon Jun 15 12:57:17 2009
|
| Stefan Ritt wrote: |
What I do is to use an editor with automatic wrapping functions, like the free PSPad editor. It nicely wraps line and indicates that:
|
Hmmm... I have to use vi and was hoping an \ at the end of the line (before the LF) would be supported. |
|