> Hi Stefan,
> 
> After 21.Oct, all the emails sent out by this discussion form now are addressed to
> 
> ELOG@ananke.jtan.com
> the name of the server my mails are sent to.
> 
> Before that the emails were addressed to 
> 
> ELOG@emix.psi.ch
> 
> Obviouisly my real email address is there, in the headers (as it would appear for a BCC)
> 
> The only consequence for me was these emails turned up in the wrong mailbox, but perhaps it has wider implications?

Indeed on Oct. 21st the SMPT server sending out emails from this forum has been changed. I checked my own mails coming 
from the forum, but I could not find any hint of what you describe above. The "From:" header contains "noreply@psi.ch" 
and the "To:" header is my email address. The "Received:" header contains our SMTP server, but you should not that field 
for filtering your email.

- Stefan

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.

 Thanks for the quick bug fix.

Bertram

Attributes = subject, ... 
Options <name> = test{1}, ...  
Subst myvar = $shell(dir) 
{1} Preset subject = Test 
{1} Preset text = $myvar 

{1} Preset text = $shell(dir)

We plan to use ELOG with mirror servers in a larger scale here, so I'm interested to know more about your problem.

Could you boil down your configuration to a minimum that still allows a reproduction of the problem and post those configurations as attachments?

Then I would try to reproduce it here. Best case I'll find a bug fix, worst case I'll reconsider the use of mirror servers ;-)

 I have been using the mirror mechanism for one year for the online T2K /ND280 (neutrino oscillation experiment at J-PARC, Japan).  It has been a savior to allow access to all collaborators to the Elog.  The experiment online computers are all behind a double firewall that allow only communication through ssh and http in one direction: from the inside to the outside. The master Elog is located in Canada and accessible remotely to all collaborators.  The mirror Elog is located inside the firewall on one of the online machines in Japan and synchronization is setup to run automatically every 5 minutes. There are 10 logbooks defined for each of the sub-detector groups.

At first I encountered a big problem when messages were added on both sides.  It turned out that Elog mirroring does not work when the two instances are running on different time zones. After I set the machine in Canada to run on Japan time (JST), no further problems have happened. Postings are routinely entered on either of the Elogs and synchronization works well.  This feature is essential to having a workable Elog for the T2K experiment. 

I had reported the problem of timezones to Stefan last year. He was going to put it on his wish list.