Version 2.3.9 of elog has been released today. Enhancements are:

- Added options "Use Lock", "Title image"

- New "Email format" specifies what is sent exactly in an email 
notification. This may now include also attachments

- "Format <attribute>" lets you assign separate style sheet classes to each 
attribute, making the web display more powerful (see this forum, 
the "subject" uses a separate formatting). Note that this feature requires 
an update of the old "default.css" CSS file, if a elog version prior to 
2.3.9 is already installed on a system.

- "Execute new/edit/delete" lets one execute shell commands on the server 
side for new, edited or deleted messages. Since this can cause security 
problems, a new flag "-x" has been added to the elogd daemon to enable this 
feature. It can be used to synchronize the elog database with other 
databases, or to send SMS messages to people.

- New "Logging level" option gives enhanced logging capabilities, including 
read and write access logging to individual elog entries.

- The elog utility can now edit existing messages, and correctly quotes 
messages with "> " on replies.

A few small bugs have been fixed, refer to the ChangeLog for more details.

Can you give a syntax example of the Logging Level option ?



> Version 2.3.9 of elog has been released today. Enhancements are:
> 
> - Added options "Use Lock", "Title image"
> 
> - New "Email format" specifies what is sent exactly in an email 
> notification. This may now include also attachments
> 
> - "Format <attribute>" lets you assign separate style sheet classes to each 
> attribute, making the web display more powerful (see this forum, 
> the "subject" uses a separate formatting). Note that this feature requires 
> an update of the old "default.css" CSS file, if a elog version prior to 
> 2.3.9 is already installed on a system.
> 
> - "Execute new/edit/delete" lets one execute shell commands on the server 
> side for new, edited or deleted messages. Since this can cause security 
> problems, a new flag "-x" has been added to the elogd daemon to enable this 
> feature. It can be used to synchronize the elog database with other 
> databases, or to send SMS messages to people.
> 
> - New "Logging level" option gives enhanced logging capabilities, including 
> read and write access logging to individual elog entries.
> 
> - The elog utility can now edit existing messages, and correctly quotes 
> messages with "> " on replies.
> 
> A few small bugs have been fixed, refer to the ChangeLog for more details.

> Can you give a syntax example of the Logging Level option ?

Please refer to the documentation (http://midas.psi.ch/elog/config.html), I just 
updated it. "Logging Level = 3" is the maximum level which includes writes and 
reads.

Cheers

It appears Im having problems getting this to work, my config is as follows, yet 
its not updating the log file since i installed the new RPM 2.3.9, is there a 
problem or am I doing something wrong ?

Thanks in advance.

[global]
port = 81
Logbook dir = /data
Logbook Tabs = 1
Main Tab = Home
Page title = LogBook System
SMTP host = support.localnet
Logfile = /var/log/elogd.log
Logging level = 3
Resource dir = /usr/local/elog
Welcome title = <img src="logo.gif"><p><font size=4 color=white>Customer Relational 
Management System</font>
Page title = Customer Relational Management System
Bottom text = bottom.html
URL = http://172.16.24.108:81/

> > Can you give a syntax example of the Logging Level option ?
> 
> Please refer to the documentation (http://midas.psi.ch/elog/config.html), I just 
> updated it. "Logging Level = 3" is the maximum level which includes writes and 
> reads.

> It appears Im having problems getting this to work, my config is as follows, yet 
> its not updating the log file since i installed the new RPM 2.3.9, is there a 
> problem or am I doing something wrong ?

Oops, there was a bug. I added the resource directory in front of the logfile name, 
which is not correct if the logfile name contains an absolute path. I fixed that in 
the current CVS version. As a temporary fix, remove the resource dir in your elogd.cfg 
or remove the full path in the logfile (the file will the be put into the resource dir 
of course...).

> Version 2.3.9 of elog has been released today. Enhancements are:

Forgive me if I've missed it, but I've looked in the forum, on-line cfg docs 
and downloaded docs.  I cannot find details on how to the used 
the "Execute ..." command.  What is passed on command line, etc.

thanks in advance
mike
 
> - "Execute new/edit/delete" lets one execute shell commands on the server 
> side for new, edited or deleted messages. Since this can cause security 
> problems, a new flag "-x" has been added to the elogd daemon to enable this 
> feature. It can be used to synchronize the elog database with other 
> databases, or to send SMS messages to people.
>

> Forgive me if I've missed it, but I've looked in the forum, on-line cfg docs 
> and downloaded docs.  I cannot find details on how to the used 
> the "Execute ..." command.  What is passed on command line, etc.

Sorry, I forgot to put it into the documentation. It's now available from 
http://midas.psi.ch/elog/config.html You basically use "Execute new = 
<command>", where <command> can have substitutions like $<attribute>, 
$remote_host, etc. You also have to start elogd with the "-x" flag to enable 
shell executions, since they can impose a security problem (see documentation).

Contribution available for all who wants to make SKIN for ELOG!

You are invited to benefit from this free info!

Just click on the "Contributions" tab to find the info (look for ID6).

Or... goto          http://midas.psi.ch/elogdemo/Contributions/6