Here is the mail log:

Jan 12 13:51:54 techies lmtpunix[3184]: dupelim: eliminated duplicate message to user.jf id <neteng-1067@emich.edu> (delivery)

The message id we are experiancing problems with is in the header;

Message-ID: <neteng-1073@emich.edu>

Thank you for the help.

I am testing Elog for personal and group use. I am starting with a Windows install on a PC. (I came across Elog when doing a shift on ATLAS at CERN.)

It took me some time to discover how to access a local logbook and create a new one. I suggest adding short sections in a prominent place in the guides:

User guide:

"Accessing a logbook: To access a logbook, point your Web browser at the appropriate URL. The default for a local Elog is http://localhost:8080/logbookname. Logbook files are stored in directory logbookname which is a sub-directory of the logbook root directory, defined by the administrator. See the administrator guide on how to create a new logbook."

Admin guide:

"Creating a logbook: A logbook is created in three steps: 1) The logbook root directory is defined as an option of the elogd start command; 2) A sub-directory, of the logbook root directory, named logbookname is created; and 3) The elogd.cfg file is edited to define the logbook's attributes and options. No files are created in the sub-directory; that is done when entries are made."

Regards,

Ken McF

Dear Ken,

first of all thanks for trying to improve the documentation. For me as the developer it's always hard to imagine what people need to know, since I know already all about elog. Therefore I ask usually other people to write the documentation. The one for elog was written by Fred Pacquier.

When going through your comments, I realize that you had some problems on your first steps. But you say you have a Windows installation. If you use the normal installer, you get some entries in your "Start" menu under Windows, with which you can directly access your "demo" logbook which comes with the installation: Start -> All Programs -> ELOG -> Demo Logbook (requires running server). To create a logbook, just access your demo logbook, then clock on "Config", then you see a button "Create new logbook". Your point 1) mentioned above is actually not necessary if you use the default root directory. It might confuse people more than it helps. Point 2) is true, but only some internal database behavior, which might not be interesting to most users.

It is possible to show the (new) text of a replied entry in the summary text field ?

Actually only for the original entries the text was shown in the text column of the summary report, not for the replies.

In principle you can adjust the number of lines shown in the summary text file with the option summary lines = x. If you increase that value, you start seeing some part of the reply. For elog itself  it is impossible to distinguish the reply text from the origial text, since some people use plain text like

with the reply sometimes below, sometimes above the original text. Other people use full HTML with tables (like in this forum), where it is very hard internally to distinguish between original and reply text. The easiest is not to quote the original text in replies, then you will see it always.

 Thank you very much for your answer.

Is there any way to invert the order of the original text and the reply text ?

You just start writing on top of the cited text 

Hi,

I'm trying to implement top groups and started with the sample configuration shown in the 'Syntax of elogd.cfg' chapter of the documentation. But now I'm facing a problem with the links in the logbook selection page.

Here's my group configuration:

Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = NT, XP

Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases
Show top groups = 1
 

The selection page for the top groups is displayed correctly, but the URL for the groups beneath the top group is incorrect. The URL for the Linux PCs group for instance is http://localhost:8080/engineering/engineering/ . The URLs for the logbooks within the Linux PCs groups is correct (e.g. http://localhost:8080/Debian/)

Has anybody an idea what's going wrong in y configuration?

Bertram