The configuration file elogd.cfg contains entries
which define the structure of logbooks and the behaviour 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] SMTP host = mailsend.your.domain [Linux] Theme = default Comment = General linux tips and tricks Attributes = Author, Type, Category, Subject Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other Options Category = General, Hardware, Software, Network, Account, Other Options Author = Stefan, Linus, unknown Required Attributes = Author [PC] Comment = Database PC installations Attributes = Location, OS, Owner Options Location = Building1, Building2 Options OS = Linux, Windows ME, Windows 2000 Required Attributes = Location, Owner Email All = name@address, othername@otheraddress Use Mail Subject = Location
The notation of the following options is such that items enclosed by "<" and ">" should be replaced by a specific string. If a value contains blanks (like a complete sentence), it should not be enclosed in quotation marks.
If a setting has a number of possible options, they are shown in the form
option1|option2|..., meaning that one of the options
(without any vertical bar) should be used. The following options are
specific to the [global] section:
Port = <port>SSL = <0 | 1>https://... to the elogd daemon. If the
URL = directive is used, make sure to use
https://... instead of http://...
there. The ELOG distribution contains a simple self-signed certificate
in the ssl subdirectory. One can replace this
certificate and key with a real ceritficate to avoid browser pop-up
windows warning about the self-signed certificate. The default for
this option is 0.
Resource dir = <directory>-s flag when starting elogd. If not specified, use
the directory where the configuration file
elogd.cfg resides. Changing this option requires
a restart of the elogd server.
Logbook dir = <directory>-d flag when starting elogd. If not specified, use
the directory where the configuration file
elogd.cfg resides. Each logbook data is stored in a
separate directory under this root directory specified by the
Subdir option. Changing this option requires a
restart of the elogd server. This directory also contains any
password file and user HTML file.
Language = <name>elogd output. Not affected by this setting are the
configuration file options and the commands specified with the optional
Menu commands and List menu
commands, which have to be specified in English and are
translated automatically by elogd. The attribute names are unaffected
by the language setting and have to be translated manually.elogd is contained in the file
eloghelp_xx.html where xx are the first two
letters of the language (like "en", "ge" and
"fr"). For new languages, a new file of that type must be
created as well.
charset = <name>elogd. Can be used to switch to Russian or Asian
fonts.
Logbook Tabs = [0|1]1
Main Tab = <string>string is used for the contents of the tab.
Main Tab URL = <string>Welcome Title = <html code><img
src="welcome.gif">. These images must be stored in the
resource directory or in the theme directory.Welcome title = <img src="welcome.jpg"><p><font size=5 color=white>Welcome to our Elog</font>
Page title = <string>Page title in the
[global] section is used for the logbook selection
page.
List page title = <string>Selection page = <file>"/" (Unix) or "\"
or "x:" (Windows).elogd can be used.
Guest Selection page = <file>Protect Selection page = 0 | 11. Default is 0.
It is necessary to put the Password file = ... into
the [global] section of the config file for this to work.
Expand Selection page = 0 | 11.
SMTP host = <host.domain>SMTP username = <username>SMTP
password can be created or modified via the
-t switch when starting elogd. This is necessary
since the password is encrypted. To set your SMPT password, enter on
the command line:
elogd -t <your password>
Logfile = <file>logging level (see below) is larger than 1,
also read and write accesses can be logged.
Logging level = 1 | 2 | 3URL =
<http[s]://host.domain[:port]/[subdir/]>elogd runs with SSL enabled
elogd runs under a proxy
then the URL under which elogd is running has to
be specified manually with this statement. The URL has to contain the
port number if not the standard port 80 is used or 433 for SSL,
and it has to contain the directory if used under a proxy like
URL = http://host.domain:8080/
|
if running on port 8080 |
URL = https://host.domain/
|
if SSL is enabled (SSL = 1) |
URL = http://host.domain/subdir/
|
if running under a proxy |
Relative redirection = 0|1Relative redirection = 1,
relative redirection is used. This uses the current URL from the browser,
whatever it is, and only specifies the last part of the URL. It should
noted however that relative redirections are not allowed in the HTTP
standard, but most browsers support it anyhow. Problems have been reported
with the Safari browser. So this option should only be used when it is
really needed.
Usr = <name>
Grp = <name>Resolve host names = 0|1hosts allow/deny options are used with host names,
this setting must be set to 1. If turned on, the DNS server is
contacted on each HTTP request to elog, which can slow down the server
considerably for slow DNS servers.
If installations have very many logbooks, it can be hard to navigate between them. To make things more structured, it is possible to build a hierarchy of logbooks. A logbook group can contain any number of logbooks as well as other logbook groups. The hierarchy is defined with the the option
Group <group name> = <Logbook1>, <Logbook2>,
<other group>
in the [global] section of the configuration file.
To define following logbook hierarchy:
one would use following statements:
[global] Group Linux PCs = Red Hat, Debian, Mandrake Group Windows PCs = 98, ME, NT, XP, CE Group CE = 1.0, 2.0
Where the selected group or logbook becomes blue. The lower groups/logbooks change according to the selected upper group. Please note that a logbook can be contained in more than one group, but then it should not be the first logbook in those groups. The colors of the tabs and the title bar can be specified in the CSS file.
Sometimes groups of logbooks should be completely separate. Imagine two
groups of logbooks, one for the engineering department and one for the
administration department. These groups should have different
administrators, and the logbook tabs at the top of the screen should not
show the logbooks from the other department. Prior to ELOG version 2.4.1,
one had to run two elogd servers in parallel, listening under different
ports. Since 2.4.1, one can achieve the same behaviour using Top
groups. The configuration could look like this:
Group Linux PCs = Red Hat, Debian, Mandrake Group Windows PCs = 98, ME, NT, XP, CE Group CE = 1.0, 2.UL Top group engineering = Linux PCs, Windows PCs Top group administration = Employees, Purchases [global engineering] Password file = engineers.pwd Admin user = stefan [global administration] Password file = admin.pwd Admin user = bill
[global] section for each
top level group of logbooks. The rule is that a configuration setting in an
individual logbook section overrides a setting in the [global
<top group>] setting, which by itsel overrides a setting
in the [global] section. This way one can define
settings for all top level groups (such as the SMTP host) in the
[global] section, and define different password files
and administrators in the individual top level group sections.http://your.host:8080/, this URL becomes invalid for
top groups, to avoid the case that one group can "see" the logbooks of the
other groups. Instead, one has to append the top group name to the URL,
such as http://your.host:8080/engineering or
http://your.host:8080/administration. If someone does
not know the top group name, one cannot see the list of logbooks there, so
the groups become completely independent of each other. If this feature is
not wanted, it can be disabled by setting Show top groups =
1.
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.
Here are the available options, by broad categories:
Data dir = <directory>Subdir = ... instead.
Subdir = <directory>elogd
program. The subdirectory is relative to the logbook root directory
specified with the Logbook dir = ... option. So if
Logbook dir = /usr/local/elog/logbooks and
Subdir = Demo then the logbook data is stored in
/user/local/elog/logbooks/Demo. If the
Logbook dir = ... option is not specified, then
logbooks is used. If the subdirectory starts with a
"/" ("\" under Windows), then it is used as an absolute path
independent of the logbook dir. To see which directories are used,
start elogd with the "-v" flag.
Comment = <comment>Theme = <theme>CSS = <filename>CSS = <file1>&<media1>,<file2>&<media2>. This will then be translated into separate style sheet
statements for the different media. For example a statement
CSS = default.css&screen,print.css&print
will result in the HTML statements:
<link rel="stylesheet" type="text/css" href="default.css" media="screen">
<link rel="stylesheet" type="text/css" href="print.css" media="print">
Title image = <string><img border=0 src="elog.gif" alt="ELOG logo">
This code can be replaced by <string> to
display a different icon file, or to display some text. The icon
image has to be present in the theme directory, which is usually
<elog root>/themes/default.
Title image URL = <URL>elog.gif icon in the theme directory. This option
should only be used if the Title image option is
not used.
Time format = <string>Time format <attribute> = <string>Date format = <string>Date format <attribute> = <string>Welcome Page = <file><h1>Welcome to the test logbook</h1> <ul> <li><a href="?cmd=new">Enter</a> a new message <li><a href="?cmd=find">Search</a> the logbook </ul>The file must be present in the resource directory. Alternatively, an absolute path can be used if the file name starts with a
"/" (Unix) or "\" or
"x:" (Windows).
Start page = <command>command can be either 0?cmd=Last to display
the last message, or any other ELog menu command in the form
?cmd=xxx. To start with the search page, one uses
Start page = ?cmd=FindPlease note that if another language than English is selected via the Language = xxx option, the commands have to be in that language as well (like "Start page = 0?cmd=Letzter" for German).
Submit Page = <file><h1>You successfully submitted a message</h1> <a href="?cmd=Back">Back</a> to the logbook<p> <a href="?cmd=New">Enter</a> another messageThe file must be present in the logbook directory. Alternatively, an absolute path can be used if the file name starts with a
"/" (Unix) or "\" or
"x:" (Windows).
Message comment = <comment>Reply comment = <comment>Attachment comment = <comment>Menu commands = <list>language = ... setting, and are automatically
translated into the specified language.Menu commands = List, New, Edit, Delete, Reply, Duplicate, Find, Config, Help
Copy to = <logbook list>
Move to = <logbook list>Copy to and Move
to make it possible to copy or move a logbook entry from one
logbook to another. By default, all logbooks except the current logbook
are shown as a possible destination. With the configurations options
Copy to = <logbook list> and Move to
= <logbook list> it is possible to specify a list of
destination logbooks, separated by commata. This can make sense if only
certain logbooks make sense as destinations. The flag Preserve IDs
can be used to keep the entry ID in the destination logbook.
List Menu commands = <list>New, Find, Select, Import, Config, Admin, Change
password, Logout and Help make sense.
The command Select can be used to select multiple
messages for deletion or for moving to other logbooks. Once the
Select command is clicked, check boxes appear in
front of all entries which let the user select one or more entries. A
new menu bar shows up with a Delete and optionally
a Coyp to ... and Move to ...
button, if these commands are present in the Menu
commands list. Pressing one of these buttons deletes, copies
or moves all selected logbook entries.
Guest Menu commands = <list>Menu commands = List, New, Edit, Reply, Duplicate, Find, Config, Logout, Help Guest menu commands = List, Find, Login, Help
Note that the presence of this option opens user access also to the
find result or elog listing page, which usually contains some config
command. So it is useful to combine the Guest menu
commands option with the following Guest List
Menu commands option to restrict the access to the find
result page as well.
Guest List Menu commands = <list>Menu text = <file><small> <a href="?cmd=next&type=Routine">Next Routine entry</a> | <a href="../?Type=Routine">All Routine entries</a> </small>
List Menu text = <file>Filter Menu text = <file>Guest Display = <list>list consists of comma
separated attributes, including the word text, if one wants to
display the entry body text for guests.
<small> <a href="?mode=summary">Summary</a> | <a href="?mode=full">Full</a> | <a href="?mode=threaded">Threaded</a> | </small>
Top text = <file> | <string>"/" (Unix) or "\" or
"x:" (Windows).
Bottom text = <file> | <string><center><a href="/">Main page</a></center>Or it can contain other useful links. If a file is specified, it must be present in the logbook directory. Alternatively, an absolute path can be used if the file name starts with a
"/" (Unix) or
"\" or "x:" (Windows).
Bottom text login = <file> | <string>Bottom text but for the login page. This
allows to display a different text at the bottom of the login page. It
can also be used to execute some JavaScript.
Help URL = <URL>Help URL option to specify
different help pages for different logbooks. It can point to a
site-specific help page via http://... or to a
local file like file://c:/tmp/config.html, or to
the name of an HTML file which must be present in the resource
directory.
Message Width = <number>Message Width
and Message Height are not given, some JavaScript
code is used which automatically resizes the message window
dynamically to fit optimally into the browser window.
Message Height = <number>Message Width
and Message Height are not given, some JavaScript
code is used which automatically resizes the message window
dynamically to fit optimally into the browser window.
Admin textarea = <cols>,<rows>Display mode = [full|summary|threaded]Entries per page = <number>Restrict edit time = <hours>Max content length = <bytes>Fonts = <list>Fonts = Arial, Comic Sans MS, Courier New, Tahoma, Times New
Roman, VerdanaAll display limit = <n>500.
Thumbnail size = <size>size gets passed to the -thumbnail
option of the conversion. A value of 300 converts
all pictures to thumbnails 300 pixels wide. A value of
300> converts all pictures to thumbnails 300
pixels wide if they are larger than 300 pixels initially, and leaves
them untouched if they are smaller. A value of 10%
converts all pictures to 10% of their original size. If the
thumbnail size option is missing, the thumbnails will be created
with the original image size, and can then be resized and rotated
interactively with the image manipulation buttons:
![]()
Setting Thumbnail size = 0 turns off the thumbnail
creation.
Thumbnail options = <options>
Attributes = <list>
since these are used internally by elog.
Options <attribute> = <list>Options town = San Francisco, "Paris, Texas", "Paris, France"
Extendable options = <list>Options <attribute> to specify
a list of possible options, this list is fixed. Sometimes it is
desirable to extend the list when a new entry in a logbook is made and
a certain option is missing on the list. By adding the attribute name
to the Extandable options list, a button appears
next to the attribute in the message entry form which lets you add new
options to the list. The elogd.cfg configuration file is then
automatically updated. When a new logbook entry gets made, the new
option automatica