Create a blank text file (called mine passwd.txt)
Place the text file somewhere in the elog directory structure
(I placed mine in c:\elog\passwd.txt because i wanted to use it globally 
for all logbooks.  I believe this forum places it in \elog\logbooks\forum 
directory).

For the Elogd.cfg:

[Forum]
; general options
Password file = c:\elog\passwd.txt
Admin user = user1
Self register = 1
Theme = default

or

[global]
logbook tabs = 1
tab cellpadding = 2
SMTP host = smtp.host.net
URL = http://myelog
Password file = c:\elog\passwd.txt
Admin user = user1
Self register = 1


For the first time logging in, Click Login from the Forum Pages, then at 
the login screen, click Register as New User
Fill out all the appropriate information
example:

Login name: user1 (seems to be case sensative)
Full name: First User
Email:  user1@email.net
Automatic email notification:  (box checked)
Password:  password (seems to be case sensative)
Retype password:  password (seems to be case sensative)

Then click Save

If you open up the passwd.txt file you should see something like:

user1:cGFzc3dvcmQ=:First User:user1@email.net:all

Some other examples based on what info you provided during the 
registration:

user1::First User:user1@email.net:all   (password left blank)
user1:cGFzc3dvcmQ=:First User:user1@email.net (NO Auto email Notify)
user1::First User::all (password and email address left blank)

If you leave the Full Name blank then the logged in user will not be 
reflected correctly in the logbook.

Hope this helps.

Eric

> Hi ,
> 
> currently I am running Elog 2.1.1; when using a konqueror browser (ver. 
> 2.2.1, kde 2.2.1) the admin user cannot access in the Config menu the Login 
> infos for other users except himself. The pulldown menu "Select user" is 
> shown, but when the admin selects another user the info fields (Login name, 
> full name, email) are not updated. They still show the attribute values for 
> the admin user himself.
> 
> Is there a solution available?
> Thanks (also for this very useful tool) and regards,
> 
> Stefan

This operation is done via Java Script, which has to be enabled in the 
browser. If anybody knows a better way, please let me know.

> Hi,
> 
> is there a documentation for the elconv tool available?
> 
> Regards,
> 
> Stefan

I have asked Fred Pacquier who maintains the web pages to put something on, 
but he hasn't replied.

Basically you simply run "elconv" in the directory where all the *.log files 
live. The only option is the "-v" flag for verbose output. If you have 
several directories with log files, you run it once in each directory.

Since the way ELOG works has changed in version 2.2.0 (show message list as 
default view), the configuration file elgod.cfg for this site became 
slightly simpler. The usual "Start page = ?cmd=Search" is not necessary any 
more due to the changed default view. The commands displaying the last x or 
last x days of messages are still working, but depreciated, since the "Show 
last xxx" facility takes care of that. The default menu commands have been 
change which reflect the modified default view. The single elog page now 
has a "back" link instead the find result page.

Here is the updated version:

======= cut here ========

[global]
logbook tabs = 1
SMTP host = mailsend.psi.ch
URL = http://midas.psi.ch/elogdemo/
user = midas
group = midas
Logout to main = 1

[Linux]
Theme = default
Comment = General linux Tips & Tricks
Data dir = /usr/local/elogdemo/logbooks/Linux
Attributes = Author, Type, Icon, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, 
Configuration, Tips & Tricks, Info, Other
IOptions Icon = icon1.gif, icon3.gif, icon4.gif, icon5.gif, icon6.gif, 
icon7.gif, icon8.gif, icon12.gif, icon13.gif, icon14.gif
Options Category = General, Hardware, Software, Network, Applications, 
Shell, Account, Packages, Daemons, Other
Required Attributes = Author
Subst Author = $author
Summary on default = 1
Summary lines = 0
Email all = stefan.ritt@psi.ch
Email message body = 1

[Database]
Theme = default
Comment = Demo of database-like elog
Data dir = /usr/local/elogdemo/logbooks/database
Attributes = Type, Operating system, Location, Status, Comment
Required Attributes = Type, Operating system, Location, Status
Options Type = PC, Router, Bridge
Options Operating system = Linux, Windows NT, Windows 2000, Windows XP, 
Windows ME, Embedded
Options Location = Building1, Building2, Building3
Options Status = working, defect, in repair
Show text = 0
Display search = #, Type, Location, Status
Summary lines = 0
Number Attachments = 0
Suppress default = 2
Entries per page = 10

[Forum]
; general options
Password file = /usr/local/elogdemo/logbooks/forum/passwd
Admin user = stefan
Self register = 2
Theme = default
Comment = Discussion forum about ELOG
Data dir = /usr/local/elogdemo/logbooks/forum
Display mode = threaded
Guest menu commands = Back, Find, Login, Help
Guest find menu commands = Find, Login, Help
Number Attachments = 1
Message comment = <img src=icons/icon6.gif> Please enter only serious 
messages here, for testing use the <b>Linux</b> Logbook:
Filtered browsing = 0
Entries per page = 8
Reverse sort = 1
Restrict edit = 1

; Attributes
Attributes = Icon, Author, Author Email, Category, Subject
Options Category = Info, Bug report, Bug fix, Question, Request, Comment, 
Other
IOptions Icon = icon1.gif, icon2.gif, icon3.gif, icon4.gif, icon5.gif, 
icon6.gif, icon7.gif, icon8.gif, icon12.gif, icon13.gif, icon14.gif
Required Attributes = Author, Author Email, Subject, Icon
Subst on reply subject = Re: $subject
Thread display = $subject, posted by $author on $Entry date
Thread icon = Icon
Remove on reply = Author, Author Email
Date format = %B %d, %Y
Preset Author = $long_name
Preset Author Email = $user_email
Locked Attributes = Author

; Email notification
Email message body = 1
Display Email recipients = 0

From: http://elog.sourceforge.net/

Solaris

It was reported by Martin Huber that under Solaris 7 following command must 
be used to compile elog:

gcc -L/usr/lib/ -ldl -lresolv -lm -ldl -lnsl -lsocket elogd.c -o elogd

It was also reported that the keep-alive mechanism is not working under some 
Solaris systems, so you need to start the elogd server with the "-k" flag to 
turn keep-alives off. 



Yep... does the job.
(even with 2.2.2 under Sol 8)

Starting from version 2.2.4 which has been released today, the 
option "quick filter" has been added. A "quick filter" is a drop down box 
on the message display page. By selecting a value from the drop down box, 
only messages of that type are displayed. See this forum which uses "Quick 
filter = Date, Category".

This new option adresses a couple of installations which require a large 
number of logbooks. Instead of using many similar logbooks, the old logbook 
name can now be defined as an attribute. All messages get now mixed, but by 
defining the logbook attribute as a quick filter, one can display the 
messages belonging to the individual logbooks separately with a single 
click.

> Was wondering if there were any tweaks/suggestions for improving the 
> logbooks responsiviness.  Our logbook was started 31 July 01.  Since that 
> time we have went from 1 logbook to 4 logbooks.  Logbook 1 having 2651 
> entries, logbook 2 having 300 entries, and the last 2 are new logbooks, so 
> only a few entries.
> 
> When user launches the logbook website, it takes considerable time to bring 
> the site up.  It seems to be directly related to the number of entries in 
> the logbook.  If I set up a dummy site with a couple logbooks and only a 
> few entries, the logbook is very fast coming up as well as saving entries.
> 
> Another thing that seems to slow the site down, is the number of users in 
> the elog notification list (those who've subscribed).  When you save a log 
> entry, it takes around 30sec or longer for it to actually complete the 
> save.  If I remove the list of users from the notification list and just 
> have a few, the save is very fast.
> 
> 
> Thanks in advance,
> 
> Eric

2600 entries is too much for this application as it load the all files 
in computer memory
expand the server memory
Are you running on linux or Windows ? I suggest linux (faster)
We are working on the C source to move all data from flat to database like 
SQL or mysql
when a parameter flag like 'status' = "OK" for instance
I suggest also to split in several logbook
but this is depend on your 'ELOG' parametrisation and logics

If your data are not 'sensitive' I can check on my linux server

Etienne

> may be add a parameter
> 
> Restrict Search all logboog = 1 or 0
> if 1 the switch will not appear 

The flag "Search all logbooks" is already there! (I forgot about it!). So 
just set it to "0" and you should be fine.

- Stefan