elog-2.0.5 core dumps under Solaris, posted by Christian Korschan on Wed Jul 24 16:44:44 2002
|
Just compiled elog-2.0.5 under Solaris 8 and 9 without any warnings/errors
but the elogd binary just core dumps:
|
Re: elog-2.0.5 core dumps under Solaris, posted by Christian Korschan on Wed Jul 24 17:24:31 2002
|
> Just compiled elog-2.0.5 under Solaris 8 and 9 without any warnings/errors
> but the elogd binary just core dumps:
>
|
Improved display speed, posted by Stefan Ritt on Tue Jul 23 15:59:55 2002
|
Version 2.0.5 of elog has been released today. Among various bugfixes, the
display speed for threaded lists has been improved significantly. Display
all messages of this forum and press the reload button to see the
|
change the Email From address used when sending notifications, posted by WootenE on Tue Jul 16 15:19:08 2002
|
Is there a way to change the From address used when sending notifications
from ELOG? I was hoping there might be another attribute that would go
along with the smtp host section.
|
Re: change the Email From address used when sending notifications, posted by Stefan Ritt on Tue Jul 23 09:16:01 2002
|
> Is there a way to change the From address used when sending notifications
> from ELOG? I was hoping there might be another attribute that would go
> along with the smtp host section.
|
Port specification with -p fails under RedHat Linux (2.0.4-1), posted by Joeri Mastop on Mon Jul 15 14:09:30 2002
|
Hello,
I noticed a strange behaviour with Elog 2.0.4 (i386 RPM) in Linux (RH 7.2).
|
Re: Port specification with -p fails (SOLVED, more or less), posted by Joeri Mastop on Mon Jul 15 15:05:22 2002
|
> Anyone seen similar problems?
Probably not if you read the config file, 'cause I didn't. Shame on me...
|
Re: Port specification with -p fails (SOLVED, more or less), posted by Stefan Ritt on Tue Jul 23 09:12:14 2002
|
> > Anyone seen similar problems?
> Probably not if you read the config file, 'cause I didn't. Shame on me...
>
|
Reverse sort, threaded display fails when there is only 1 entry in logbook, posted by Ravi Pappu on Sun Jul 14 15:15:19 2002
|
This is not a serious bug...but when the global settings are as follows
|
Re: Reverse sort, threaded display fails when there is only 1 entry in logbook, posted by Stefan Ritt on Wed Jul 17 14:53:18 2002
|
>
>
> This is not a serious bug...but when the global settings are as follows
|
last x link TEXT, posted by H. Scheit on Fri Jul 12 10:18:21 2002
|
The last x link TEXT now shows up like this
|
Re: last x link TEXT, posted by Stefan Ritt on Fri Jul 12 10:26:40 2002
|
> The last x link TEXT now shows up like this
>
> 'Last 20 entries?mode=threaded'
|
entry number not updated properly after deleting, posted by mo on Thu Jul 11 15:59:17 2002
|
Hello,
If you delete a message from the middle of a logbook that contains a
bunch of messages, the message numbers do not get updated properly. For
|
Re: entry number not updated properly after deleting, posted by Stefan Ritt on Thu Jul 11 16:03:56 2002
|
> Hello,
> If you delete a message from the middle of a logbook that contains a
> bunch of messages, the message numbers do not get updated properly. For
|
elog submit without user and password, posted by H. Scheit on Mon Jul 8 19:42:13 2002
|
With elog it is possible to submit messages to a password protected
logbook without specifying the -u option. I.e. NO PASSWORD is
necessary to submit a message. I assume it is related to the problem
|
Re: elog submit without user and password, posted by Stefan Ritt on Tue Jul 9 10:58:18 2002
|
> With elog it is possible to submit messages to a password protected
> logbook without specifying the -u option. I.e. NO PASSWORD is
> necessary to submit a message. I assume it is related to the problem
|
Re: elog submit without user and password, posted by H. Scheit on Tue Jul 9 15:28:33 2002
|
> > With elog it is possible to submit messages to a password protected
> > logbook without specifying the -u option. I.e. NO PASSWORD is
> > necessary to submit a message. I assume it is related to the problem
|
Re: elog submit without user and password, posted by Stefan Ritt on Wed Jul 10 08:53:21 2002
|
> I guess it cannot and doesn't have to be 100% save. Maybe if the web
> interface is used for a new message a long random number (let's call
> it newID) can be included, which elog remembers for some time (say 1
|