Syntax of elogd.cfg

The configuration file elogd.cfg contains entries which define the structure of logbooks and the behavior of elogd. The file has a simple ASCII format. Each logbook is defined by a [<name>] section where <name> is the name of the logbook. The [global] section is used for settings common to all logbooks. Each line contains a setting name, followed by an equal sign and the value for this setting. Lines starting with ";" are treated as comments.

Here is a simple example, which define two logbooks "Linux" and "PC":

Global options

Following options are possible in the [global] section:

Individual logbook options

For each logbook, there is a section with the logbook name in square brackets, so that each logbook can have different options. If an option is not present in a logbook section, then the system tries to locate that option in the [global] section. Thus if the following options are placed in the [global] section, they are defaults for all logbooks. If they are present in the [global] and in the logbook section, the logbook option is used.

Following options are available:

General options

Attributes

Access control

Reading and writing into logbooks can be constraind using two different access methods, either with global passwords for read, write and admin (config, delete), or with user- level passwords. For these two schemes to work properly, cookies have to be turned on in your browser. Please consult your browser documentation about how to do that.

EMail notification

Flags

Themes

Themes are layout and color schemes which determine the look and feel of a logbook. Each theme resides in a separate subdirectory and is specified with the theme = <dir> option in the configuration file. The directory contains the file theme.cfg and a couple of images, which are used for the title banner and the browse buttons. A default theme is contained in the distribution. If new themes are developed by users, they can send them back to the author, so they can be included in future releases.

Most of the options in the theme.cfg are self-explanatory, the colors are coded as #RRGGBB, where RR is a 8-bit hexadecimal value for the red part, GG for the green and BB for the blue part, repectively. Since theme configuration files are re-read at each access, the elogd daemon does not have to be restarted after a change in the theme configuration file.

Following two images display the same logbook page using different themes:

  

Wishlist

Here are items requested by users. I will work down the list when I have time. If you find a feature you find useful on the list, there is a good chance that you get it in a future release. You can vote for a feature by sending me an email.

FeatureVotes
Get message from standard input in elog submission program1
Users can only edit their own entries1
Make user file editable through web interface1
Implement groups of users1
Add email address field to user file, so that user name can be specified for "Email <attribute> <value> =" option which gets automatically substituted by email address1
Change internal database format from offset oriented to index oriented (lots of work, need also conversion program)2
Implement new listing mode in between "summary only" and "full listing" where a few text lines are displayed below the attribute fields1

Back to Elog home page

Stefan Ritt, May 23rd, 2001