Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 24 of 806  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
icon5.gif   Setting From: for registration/password e-mails, posted by Ben Waugh on Fri Feb 16 12:08:19 2007 
We had a problem, as mentioned in the documentation, with "new password" e-mails being rejected because the default From: address is invalid, so we changed
this using "Use Email From".
icon4.gif   'Full' mode gives incorrect results when searching, posted by Bartjan Wattel on Wed Jul 14 11:45:46 2004 
Hi, 

I was just searching your online discussion forum for entries with the 
    icon5.gif   Re: How to construct different logbooks with the same logbook options, posted by Bartjan Wattel on Wed Jul 14 11:49:26 2004 
> > I know I can simply copy the settings for logbook B and repeat the settings 
> > for all logbooks C-S. But is there a better way to accomplish this?
icon5.gif   Always suppress email notifications, posted by Bartjan Wattel on Wed Jul 14 13:31:33 2004 
Hi - again a configuration question.

How can I suppress all email notifications? The "Suppress default = 2" flag 
icon3.gif   Request: limit size of attachments, posted by Bartjan Wattel on Wed Jul 14 13:58:26 2004 
hi again,

we have been doing a bit of stress testing for Elog. The most important 
icon5.gif   ELOG with stunnel won't show logbook, posted by Bartjan Wattel on Wed Aug 25 13:36:56 2004 
Hi,

I have an ELOG installation on a RedHat linux server, called myserver. I 
Entry   Possible bug in elogd execute_shell, posted by Nigel Warr on Fri Feb 26 08:38:06 2016 
I was just playing around with gcc6's new feature for warning about misleading indentation (which can often hide real bugs) and I think it found
one in elog-3.1.1-1 at src/elogd.c:22538. Here there is an if statement, which looks as though it should be inside a loop, but it isn't.
The code is:
icon4.gif   Possible bug in elogd execute_shell, posted by Nigel Warr on Fri Feb 26 08:47:22 2016 
I was just playing around with gcc6's new feature for warning about misleading indentation (which can often hide real bugs) and I think it found
one in elog-3.1.1-1 at src/elogd.c:22538. Here there is an if statement, which looks as though it should be inside a loop, but it isn't.
The code is:
ELOG V3.1.5-3fb85fa6