> Can you consider implementing the following additions to the functionality
> 
> 1) Subt on edit <attribute> = xyz 
> 
> This would be fantastic for implementing version control so you can see 
who 
> has edited a posted or a db entry.

Can you give me an example of how you would use that?
 
> 2) Have a SORT fieldname flag so you can decide which column to sort 
things 
> by on a display listing in conjunction to the display flags, it current 
> defaults to the # column and I find i am directly linking to a sorted 
> display

Sorting is not done by the "#" column but by the sequence when messages have 
been entered. You can sort the table differently by clicking on the table 
titles (twice for reverse sort). To sort by default on a column, for example 
sort by the author, you can add

Start page = ?sort=author

into elogd.cfg which does the job.

> 3) Have the elogd.conf track actual log entries people have changed 
> detailing date and time etc.

Revision management is not forseen by the structure of the ELOG database. 
What you can do is if you edit a message you check "Resubmit as new entry", 
then you keep a copy of the old version. 

> 4) Ability to export contents of the log books to files on disk for backup 
> purposes as all data is contained within a single log file which causes 
> problem for command line searches.

Well, you have already all log book files on disk in a simple format:

YYMMDDa.log

(Year/Month/Day) which you can easily backup. By a mask like 02*a.log you 
can backup all data from 2002 and so on. The idea of having separate log 
files for each day is to have this possibility to simply backup various date 
intervals. 

What kind of command line searches are you interested in?

- Stefan

I noticed the site has been updated as far as the documentation for 2.3.1, 
however the latest version in the downloads section is 2.3.0, any other 
places where I can get 2.3.1

Cheers

> I noticed the site has been updated as far as the documentation for 2.3.1, 
> however the latest version in the downloads section is 2.3.0, any other 
> places where I can get 2.3.1
> 
> Cheers

Patience, patience! 2.3.1 is currently kind of in "beta" version, but will be 
released this week. Not that you can always get the latest snapshot from the 
CVS tree at

http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c

- Stefan

To obtain the newest source code of ELOG, go to the CVS repository at

http://midas.psi.ch/cgi-bin/cvsweb/elog/src

It contains usually the newest bug fixes, which will show up in the next 
realease. On the other hand it can also contain some new features, which 
are not yet fully tested, so care should be taken when using it. The 
revision comments usually explain what is new in that revision.

> Stefan and friends,
> 
> without breaching your own security, could it be possible to see what the 
> elogd.cfg file looks like, also if others would like to post theirs, this 
> would be great in building exmaples etc, obviosly an security related or 
> mail server entries hashed out.

Ok, good idea. I made a new logbook "Config Examples" on this server, where 
everybody can add new configuration examples. I added a few covering the 
logbooks on this server as a starting point. Just click on "Config Examples" 
at the top of this page!

Hello Stefan,

it would be useful, if the web server automatically produced tags <A NAME=
[AttachNo3]>Anhang 3</A> around the entry of the attachment. With this one 
could easily reference in the HTML text an attachement at the end of the 
page.

I had a problem, when I just put a HTML text with <IMG> tags into the 
formular box and I could not reference them although they were available 
(and displayed pictures) as attachments.

Thomas

> I checked my mail program and 
> found out that it converts a single dot into two dots at the beginning 
> of the line. I have to implement this in elgod.c.

I implemented that (->CVS): a <CR><LF>.<CR><LF> is replaced by 
<CR><LF>..<CR><LF> in email notifications. Now I don't know if all browsers 
under all OS's send a <CR><LF> on line break. If some don't, please let me 
know.

UltraEdit Syntax coloring
=========================
add this file in ultraedit
UltraEdit --> ADVANCED --> CONFIGURATION --> SYNTAX HIGHLIGHTING
I hope this will help you...

it gives different color according to elog commands
some attributes are use internaly like

ShellOnSubmit
ShellParam

if somebody has other suggestion to improve the display ask me