UPDATE:

After days of head banging and trying different syntax combinations, I finally stumbled on my own answer. It involved some syntax adjustments, and then splitting the task into these two consecutive operations:

      1. wget --no-check-certificate --cookies=on --save-cookies cookies.txt --keep-session-cookies -O e:\export1.csv "http://localhost:8080/demo/?uname=agrant&upassword=skipper"

      2. wget --no-check-certificate --cookies=on --load-cookies cookies.txt --keep-session-cookies -O e:\export2.csv http://localhost:8080/demo/?mode=CSV1

All is working fine now.

Hello,

What is the procedure to delete a logbook (incl. attachments)?

Steve

Deleting a logbook in the config page (via "Delete this logbook") only removes the logbook defiition from the config file. To really erase all information you have to go to the file system and delete the whole directory belonging to that logbook. You have one subdirectory per year, containing all logobok entries and also attachments, so make sure you do a recursiver directory removal.

Stefan

Stefan,

Thank you that is exactly what I needed to know.

Steve

We have always had issues with eLOG crashing intermittently...  I upgraded from Server 2003 to Server 2008 about a year ago to try to reduce the issues...  which really didn't help.

The service now seems to crash every week...  (getting worse)...  Is anyone seeing these issues in Windows servers?  Any suggestions??

We do run ELOG on a Linux server and see about weekly crashes, too. It seems to be connected to the authentication process (Kerberos, File), but we could not nail it down yet.

But we have set up a supervision process that checks every minute if the "elogd" process is still running. If not, it simply restarts it.

If ELOG is down for two minutes a week, this is fine for our users.

I have Split Elog to Two Top Group [Check the Config Below].

Problem = 

After Staff01 login successfully to http://127.0.0.1/Staff and if he/she fill the url http://127.0.0.1/Administrator and choose any elog topic, it will direct registration form.

[global]
port = 8080
Self register = 0
Show top groups = 1
Preset Author = $long_name
Locked Attributes = Author
Restrict edit = 1

Top group Staff = Website, Notes
Top group Administrator = Website Update, Admin Notes, Ticketing

[global Staff]
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config
Password file = staff.pwd
Admin user = sylpid
Login user = staff01

[global Administrator]
Password file = admin.pwd
Admin user = sylpid
Login user = admin01

It would be new to me if elog would support independent [global] sections for each logbook.
I thought you can only have one [global] section. Whatever is defined in that section will be valid for all logbooks.

If you need to have different user files, you'll need to run different elogd services with independent config files (and Password files).

Andreas