mirror of
https://gitea.psi.ch/ELOG/elog.git
synced 2026-09-08 17:13:56 +00:00
1 line
198 KiB
JavaScript
1 line
198 KiB
JavaScript
var __index = {"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"index.html","title":"The ELOG Home Page","text":"<p>Home of the Electronic Logbook package by Stefan Ritt</p> <p>Current version: 3.1.5</p> <p>PDF version</p>"},{"location":"index.html#what-is-elog","title":"What is ELOG ?","text":"<p>ELOG is part of a family of applications known as weblogs . Their general purpose is :</p> <ol> <li>to make it easy for people to put information online in a chronological fashion, in the form of short, time-stamped text messages (\"entries\") with optional HTML markup for presentation, and optional file attachments (images, archives, etc.)</li> <li>to make it easy for other people to access this information through a Web interface, browse entries, search, download files, and optionally add, update, delete or comment on entries.</li> </ol> <p>ELOG is a remarkable implementation of a weblog in at least two respects :</p> <ul> <li>its simplicity of use : you don't need to be a seasoned server operator and/or an experimented database administrator to run ELOG ; one executable file (under Unix or Windows), a simple configuration text file, and it works. No Web server or relational database required. It is also easy to translate the interface to the appropriate language for your users.</li> <li>its versatility : through its single configuration file, ELOG can be made to display an infinity of variants of the weblog concept. There are options for what to display, how to display it, what commands are available and to whom, access control, etc. Moreover, a single server can host several weblogs, and each weblog can be totally different from the rest.</li> </ul>"},{"location":"index.html#screen-shots","title":"Screen shots","text":"<p>On the left upper panel is a typical logbook page displayed by Netscape Navigator. Each logbook page can contain attachments in a similar way to emails. This makes it possible to store images or text files and retrieve them easily. You could for example attach a sample configuration file which can later be copied to the local machine with the \"Save As...\" function of the Web browser.</p> <p>Several logbooks can be served though a single ELOG server. Each logbook can use different attributes for its entries. The logbook can then be searched using these attributes. The right pane on the left image shows a search for all entries with attribute \"Type\" equal to \"Configuration\", and the lower pane shows the search result. It is also possible to use full-text search in attributes and the entry body. </p> <p>While logbook entries are usually displayed one entry per page, they can also be listed consecutively which makes it easy to produce a paper printout of a logbook. </p> <p>Logbook pages can be edited or deleted. This feature can be turned off in the configuration file so that a logbook entries cannot be changed after being submitted. </p> <p>An additional feature is the automatic generation of a notification email messages based on a certain type or category of a logbook entry. </p> <p>Also try out the online demo</p>"},{"location":"index.html#use-cases","title":"Use cases","text":"<p>The features of ELOG make it useful for several applications:</p> <ul> <li>Personal Logbooks. Personal notes can be written into ELOG and can then be retrieved from anywhere with a Web browser. This makes it handy for PC supporters who have to go around in companies or laboratories and don\\'t want to carry their paper logbook with them. The same holds true for people traveling around a lot. The logbook database consists of plain ASCII files which can copied easily between different computers to have local access, for example on a notebook with no network connection.</li> <li>Shared Logbooks. Logbooks can be shared by several people, for reading and optionally for writing. This way workgroups can share and exchange information like in a (simplified) news group. This is supported by the Reply command in ELOG which creates \"threads\" of entries. Users can be notified by email when new entries are added to the logbook. Compared to that of a news server, the installation of ELOG is much simpler.</li> <li>Small Databases. Since arbitrary attributes can be defined for a logbook, it can be used as a small database with search facilities.</li> <li>Problem collections. A system can consist of two logbooks, in one of which users enter bugs or problems. If someone adds a problem, an email is automatically sent to the administrator, who can then copy the entry to the second logbook and add the solution to the problem. Users can then look up all fixed problems.</li> <li>Shift Logbooks. If the Allow delete and Allow edit flags are off, an entry cannot be modified once it\\'s been entered. This can be useful for shift logbooks for example in accelerator control rooms where each entry becomes a \"document\" with a time and author stamp. ELOG was originally developed as a shift logbook for the PiBeta and Muegamma particle experiments at PSI.</li> <li>File collections. Since files can be attached to ELOG entries, the system can be used to store and retrieve files. This can be used to store configuration files, which need to be accessible by several people over the web, or to store images. Since ELOG features an elaborate query facility, entries can be searched for by specifying several categories.</li> </ul>"},{"location":"index.html#license","title":"License","text":"<p>ELOG is released under the GNU Public License .</p>"},{"location":"index.html#credits","title":"Credits","text":"<p>The author would like to give credits to following people:</p> <ul> <li>Fred Pacquier for this Web site and the French translation</li> <li>Recai Oktas and Roger Kalt for the Debian package</li> <li>djek for the Dutch translation</li> <li>Heiko Scheit for many bug fixes and fruitful discussions</li> <li>Julio Calvo for the Spanish translation</li> <li>Emiliano 'AlberT' Gabrielli for his idea of scaling attached images</li> <li>Andreas Luedeke for continuing user support and deployment of ELOG at PSI</li> </ul>"},{"location":"index.html#talks-and-presentations","title":"Talks and presentations","text":"<p>Here are some talks and presentations given at various occasions:</p> <ul> <li>Seminar at KIT, Karlsruhe, Jan. 2015. Introduction talk by Stefan Ritt.</li> <li>Seminar at KIT, Karlsruhe, Jan. 2015. Application of ELOG for accelerator operation at PSI by Andreas Luedeke.</li> </ul> <p>Content by Stefan Ritt, Web pages by Fred Pacquier</p>"},{"location":"adminguide.html","title":"ELOG Administrator's Guide","text":"<p>How to set up and run your very own ELOG server</p>"},{"location":"adminguide.html#installing-and-running-on-linux","title":"Installing and running on Linux","text":""},{"location":"adminguide.html#installation-from-the-rpm-file","title":"Installation from the RPM file","text":"<p>Since version 2.0, ELOG contains a RPM file which eases the installation. Get the file <code>elog-x.x.x-x.i386.rpm</code> from the <code>[download](http://elog.psi.ch/elog/download/RPMS/)</code> section and execute as root <code>\"rpm -i elog-x.x.x-x.i386.rpm\"</code>. This will install the <code>**elogd**</code> daemon in <code>/usr/local/sbin</code> and the <code>elog</code> and <code>elconv</code> programs in <code>/usr/local/bin</code>. The sample configuration file <code>elogd.cfg</code> together with the sample logbook will be installed under <code>/usr/local/elog</code> and the documentation goes to <code>/usr/share/doc</code>. The elogd startup script will be installed at <code>/etc/rc.d/init.d/elogd</code>. To start the daemon, enter `</p> <ul> <li><code>/etc/rc.d/init.d/elogd start</code></li> </ul> <p>It will listen under the port specified in <code>/usr/local/elog/elogd.cfg</code> which is 8080 by default. So one can connect using any browser with the URL:</p> <ul> <li><code>http://localhost:8080</code></li> </ul> <p>To start the daemon automatically, enter:</p> <ul> <li><code>chkconfig --add elogd</code> <code>chkconfig --level 345 elogd on</code></li> </ul> <p>which will start the daemon on run levels 3,4 and 5 after the next reboot.</p> <p>Note that the RPM installation creates a user and group <code>elog</code>, under which the daemon runs.</p> <p>To start the daemon on non-RedHat systems, like SuSE or Solaris, a more generic startup scrips has been provided by Steve Jones in the Contributions section.</p>"},{"location":"adminguide.html#installation-from-the-tarball","title":"Installation from the tarball","text":"<p>Download the latest <code>elog-x.x.x.tar.gz</code> package.`</p> <p>Make sure you have the libssl-dev package installed. Consult your distribution for details.</p> <p>Expand the compressed TAR file with <code>tar -xzvf elog-x.x.x.tar.gz</code>. This creates a subdirectory <code>elog-x.x.x</code> where x.x.x is the version number. In that directory execute <code>make</code>, which creates the executables <code>elogd</code>, <code>elog</code> and <code>elconv</code>. On some systems like OpenBSD you have to execut <code>gmake</code>. These executables can then be copied to a convenient place like <code>/usr/local/bin</code> or <code>~/bin</code>. Alternatively, a <code>\"make install\"</code> will copy the daemon <code>elogd</code> to <code>SDESTDIR</code> (by default <code>/usr/local/sbin</code>) and the other files to <code>DESTDIR</code> (by default <code>/usr/local/bin</code>). These directories can be changed in the Makefile. The <code>elogd</code> executable can be started manually for testing with : `</p> <p><code>elogd -p 8080</code></p> <p>where the -p flag specifies the port. Without the -p flag, the server uses the standard WWW port 80. Note that ports below 1024 can only be used if <code>elogd</code> is started under root, or the \"sticky bit\" is set on the executable.</p> <p>When <code>elogd</code> is started under root, it attaches to the specified port and tries to fall-back to a non-root account. This is necessary to avoid security problems. It looks in the configuration file for the statements <code>Usr</code> and <code>Grp.</code>. If found, <code>elogd</code> uses that user and goupe name to run under. The names must of course be present on the system (usually <code>/etc/passwd</code> and <code>/etc/group</code>). If the statements <code>Usr</code> and <code>Grp.</code> are not present, <code>elogd</code> tries user and group <code>elog</code>, then the default user and group (normally <code>nogroup</code> and <code>nobody</code>). Care has to be taken that <code>elogd</code>, when running under the specific user and group account, has read and write access to the configuration file and logbook directories. Note that the RPM installation automatically creates a user and group <code>elog</code>.</p> <p>If the program complains with something like \"cannot bind to port...\", it could be that the network is not started on the Linux box. This can be checked with the <code>/sbin/ifconfig</code> program, which must show that <code>eth0</code> is up and running.</p> <p>The distribution contains a sample configuration file <code>elogd.cfg</code> and a demo logbook in the demo subdirectory. If the <code>elogd</code> server is started in the elogd-x.x.x directory, the demo logbook can be directly accessed with a browser by specifying the URL http://localhost:8080 (or whatever port you started the elog daemon on). If the <code>elogd</code> server is started in some other directory, you must specify the full path of the <code>elogd</code> file with the \"-c\" flag and change the Data dir = option in the configuration file to a full path like /usr/local/elog.</p> <p>Once testing is complete, <code>elogd</code> will typically be started with the <code>-D</code> flag to run as a daemon in the background, like this :</p> <p><code>elogd -p 8080 -c /usr/local/elog/elogd.cfg -D</code></p> <p>Note that it is mandatory to specify the full path for the <code>elogd</code> file when started as a daemon.</p> <p>To test the daemon, connect to your host via :</p> <p><code>http://your.host:8080/</code></p> <p>If port 80 is used, the port can be omitted in the URL. If several logbooks are defined on a host, they can be specified in the URL :</p> <p><code>http://your.host/<logbook></code></p> <p>where <code><logbook></code> is the name of the logbook.</p> <p>The contents of the all-important configuration file <code>elogd.cfg</code> are described in Config.</p>"},{"location":"adminguide.html#notes-for-various-platforms","title":"Notes for various platforms","text":"<p>This section contains notes for installing and running elog under various operating systems.</p>"},{"location":"adminguide.html#mac-os-x","title":"Mac OS X","text":"<p>Under Mac OSX, ELOG must be compiled from the source code. The OSX command line tools (compiler & Co) must be available, which can be done thought he free Xcode package which can be obtained though the App Store. Once Xcode is installed, you can do a <code>xcode-select --install</code> to install the command line tools. After that, a simple <code>make</code> in in the elog directory does the job of compiling ELOG. If SSL support is needed (access via https://...), you have to install OpenSSL and turn on SSL support in the Makefile by setting <code>USE_SSL = 1</code>. You can install OpenSSL for example through the MacPorts project. After having installed MacPorts, you do a <code>sudo port install openssl</code>.</p> <p>After successful compilation, you do a <code>sudo make install</code> to install all required files under the installation directory, which is by default <code>/usr/local/</code>. A subdirectory <code>/usr/local/elog</code> is created which contains a simple example logbook. The ELOG server can now be started either manually with</p> <p><code>/usr/local/sbin/elogd</code></p> <p>or through the daemon servics with</p> <pre><code>sudo launchctl enable system/ch.psi.elogd\nsudo launchctl bootstrap system /Library/LaunchDaemons/ch.psi.elogd.plist\n</code></pre> <p>To stop the service, use</p> <pre><code>sudo launchctl bootout system /Library/LauchDaemons/ch.psi.elogd.plist\nsudo launchctl disable system/ch.psi.elogd\n</code></pre>"},{"location":"adminguide.html#debian","title":"Debian","text":"<p>A Debian package is available under https://tracker.debian.org/pkg/elog.</p>"},{"location":"adminguide.html#solaris","title":"Solaris","text":"<p>Martin Huber reports that under Solaris 7 the following command line is needed to compile elog:</p> <p><code>gcc -L/usr/lib/ -ldl -lresolv -lm -ldl -lnsl -lsocket elogd.c -o elogd</code></p> <p>With some combinations of Solaris servers and client-side browsers there have also been problems with ELOG's keep-alive feature. In such a case you need to add the \"-k\" flag to the <code>elogd</code> command line to turn keep-alives off.</p>"},{"location":"adminguide.html#freebsd","title":"FreeBSD","text":"<p>David Otto maintains the ELOG port for FreeBSD. To install ELOG on a FreeBSD system, you can simply type</p> <pre><code>cd /usr/ports/www/elog\nmake install clean\n</code></pre>"},{"location":"adminguide.html#running-elogd-under-apache","title":"Running elogd under Apache","text":"<p>For cases where <code>elogd</code> should run under port 80 in parallel to an Apache server, Apache can be configured to run Elog in a subdirectory of Apache. Start <code>elogd</code> normally under port 8080 (or similarly) as noted above and make sure it's working there. Then put following redirection into the Apache configuration file:</p> <pre><code>Redirect permanent /elog http://your.host.domain/elog/\nProxyPass /elog/ http://your.host.domain:8080/\n</code></pre> <p>Make sure that the Apache modules mod_proxy.c and mod_alias.c are activated. Justin Dieters \\<enderak@yahoo.com> reports that mod_proxy_http.c is also required. The Redirect statement is necessary to automatically append a \"/\" to a request like <code>http://your.host.domain/elog</code>. Apache then works as a proxy and forwards all requests staring with <code>/elog</code> to the elogd daemon.</p> <p>Note: Do not put <code>\"ProxyRequests On\"</code> into your configuration file. This option is not necessary and can be misused for spamming and proxy forwarding of otherwise blocked sites.</p> <p>Because <code>elogd</code> uses links to itself (for example in the email notification and the redirection after a submit), it has to know under which URL it is running. If you run it under a proxy, you have to add the line:</p> <p><code>URL = http://your.proxy.host/subdir/</code></p> <p>into elogd.cfg.</p>"},{"location":"adminguide.html#using-apache-authentication","title":"Using apache authentication","text":"<p>It is also possible to login via an apache-auth module. In elogd.cfg you should use the keyword \"Webserver\" for Authentication:</p> <p><code>Authentication = Webserver</code></p> <p>This triggers elogd to use the environment variable \"X-Forwarded-User\" as the logged in user. A simple example of a apache configuration (including the proxy) is :</p> <pre><code># this required to pass on the generated env-variable X-Forwarded-User to the proxy \nProxyPassInterpolateEnv On\n\nProxyPass /elog/ http://your.host.domain:8080/\n\n<Location \"/elog\">\n Order allow,deny\n Allow from all \n AuthType Basic\n AuthName \"elog-server\"\n AuthUserFile \"/opt/elog/htpasswd\"\n require valid-user\n RequestHeader unset Authorization\n RequestHeader add X-Forwarded-User %{REMOTE_USER}s\n # elog doesn't like the '@', so we need to cut it\n RequestHeader edit X-Forwarded-User \"@(.*)$\" \"\"\n</Location>\n</code></pre>"},{"location":"adminguide.html#installing-imagemagick","title":"Installing ImageMagick","text":"<p>When images are attached to ELOG entries, thumbnails can be created for quick preview. This works also for PDF and PostScript files. ELOG forwards any image operation to the ImageMagic and GhostScript packages, which must be installed for this to work. While these packages are installed on most Linux systems, windows users have to download and install these pagages manually. ImageMagick can be obtained from www.imagemagick.org and GhostScript can be obtained from http://pages.cs.wisc.edu/~ghost/. After the installation, it has to be made sure that both packages are in the path. This can be checked to open a command prompt and typing <code>identify -version</code>. This command should return someting like:</p> <pre><code>C:\\>identify -version\nVersion: ImageMagick 6.3.8 01/25/08 Q16 http://www.imagemagick.org\nCopyright: Copyright (C) 1999-2008 ImageMagick Studio LLC\n</code></pre> <p>When ELOG is started interactively, it checks for the ImageMagick installation and shows a note if it is found:</p> <pre><code>C:\\Program Files\\ELOG>elogd\nelogd 2.7.2 built Feb 21 2008, 20:00:42 revision 2051\nImageMagick detected\nIndexing logbooks ... done\nServer listening on port 8080 ...\n</code></pre> <p>If ImageMagick is not installed, the thumbnail functions are simply disabled, but ELOG can otherwise run normally.</p>"},{"location":"adminguide.html#installing-and-running-in-windows","title":"Installing and running in Windows","text":"<p>ELOG is distributed in binary (executable) form for Windows platforms. It will run happily in console mode (or \"DOS box\") under Windows 9x and ME. Under Windows NT and 2000 it is also possible to run it as a service (the Windows equivalent of a UNIX daemon).</p> <p>Download the latest <code>elogxxx.exe</code> file and execute it. The installer puts the ELOG system into a directory you specify and adds some menu shortcuts. With these shortcuts, the daemon <code>elogd.exe</code> can be started directly and the demo logbook can be accessed with the browser. Alternatively, the <code>elogd.exe</code> daemon can be registered as a service under Windows NT/2000/XP, so it gets started automatically when windows boots. This can be selected during installation or be done manually with the start menu shortcuts.</p> <p>While the pre-2.5.3 methods of installing elogd.exe as a daemon (namely FireDaemon and srvany.exe) are still possible, they are not recommended any more.</p> <p>Under Windows, the ports below 1024 can be used without restriction. So if no web server is running on the same PC the ELOG daemon can be started under the standard Web port 80. This is achieved by changing the <code>port=8080</code> option in <code>elogd.cfg</code> to <code>port=80</code><code>and restarting elogd.</code></p>"},{"location":"adminguide.html#server-configuration","title":"Server Configuration","text":"<p>[The ELOG daemon <code>elogd</code> can be executed with the following options :]{#config}</p> <pre><code>elogd [-p port] [-n hostname/IP] [-C] [-m] [-M] [-D] [-c file] [-s dir] [-d dir] [-v] [-k] [-f file] [-x]\n\nwith :\n\n`-p <port>`\u00a0 TCP port number to use for the http server (if other than 80)\n`-n <hostname or IP address>` in the case of a \"multihomed\" server, host name or IP address of the interface ELOG should run on\n`-C <url>`\u00a0 clone remote elogd configuration\u00a0\n`-m`\u00a0 synchronize logbook(s) with remote server\n`-M`\u00a0 synchronize with removing deleted entries\n`-l <logbook>`\u00a0 optionally specify logbook for -m and -M commands\n`-D`\u00a0\u00a0 become a daemon (Unix only)\n`-c <file>`\u00a0 specify the configuration file (full path mandatory if -D is used)\n`-s <dir>` specify resource directory (themes, icons, \\...)\n`-d <dir>` specify logbook root directory\n`-v\u00a0 ` verbose output for debugging\n`-k\u00a0 ` do not use TCP keep-alive\n`-f <file>`\u00a0specify PID file where elogd process ID is written when server is started\n`-x\u00a0 `enables execution of shell commands\n</code></pre> <p>The appearance, functionality and behaviour of the various logbooks on an ELOG server are determined by the single <code>elogd.cfg</code> file in the ELOG installation directory.</p> <p>This file may be edited directly from the file system, or from a form in the ELOG Web interface (when the Config menu item is available). In this case, changes are applied dynamically without having to restart the server. Instead of restarting the server, under Unix one can send a HUP signal like <code>\"killall -HUP elogd\"</code> to tell the server to re-read its configuration.</p> <p>The many options of this unique but very important file are documented on the separate elogd.cfg syntax page.</p> <p>To better control appearance and layout of the logbooks, <code>elogd.cfg</code> may optionally specify the use of additional files containing HTML code, and/or custom \"themes\" configurations. These need to be edited directly from the file system right now.</p> <p>The meaning of the directory flags <code>-s</code> and <code>-d</code> is explained in the section covering the configuration options <code>Resource dir</code> and <code>Logbook dir</code> in the elogd.cfg description.**</p>"},{"location":"adminguide.html#secure-connections-howto","title":"Secure Connections HOWTO","text":""},{"location":"adminguide.html#using-elogd-itself","title":"Using elogd itself","text":"<p>Starting from version 2.7.3 on, the <code>elogd</code> program supports secure connections over the Secure Socker Layer (SSL) directly. It is recommented to run elog only through secure HTTPS connections if passwords are used. Otherwise the passwords are send over the network in clear text and exposed to sniffing attacks. To use SSL, put <code>SSL = 1</code> into the config file. If the <code>URL =</code> directive is used, make sure to use <code>https://...</code> instead of <code>http://...</code> there. The ELOG distribution contains a simple self-signed certificate in the <code>**ssl**</code> subdirectory. One can replace this certificate and key with a real ceritficate to avoid browser pop-up windows warning about the self-signed certificate. `</p>"},{"location":"adminguide.html#using-apache","title":"Using Apache","text":"<p>Another possibility is to use the Apache web server as a proxy server allowing secure connections. To do so, Apache has to be configured accordingly and a certificate has to be generated. See some instructions on how to create a certificate, and see Running elogd under Apache before on this page on how to run elogd under Apache. Once configured correctly, elogd can be accessed via http://your.host and via https://your.host simultaneously.</p> <p>The redirection statement has to be changed to</p> <pre><code>Redirect permanent /elog https://your.host.domain/elog/\nProxyPass /elog/ http://your.host.domain:8080/\n</code></pre> <p>and following has to be added to the section \"VirtualHOst ...:443 in /etc/httpd/conf.d/ssl.conf:</p> <pre><code># Proxy setup for Elog\n<Proxy *>\nOrder deny,allow\nAllow from all\n</Proxy>\nProxyPass /elog/ http://host.where.elogd.is.running:8080/\nProxyPassReverse /elog/ http://host.where.elogd.is.running:8080/\n</code></pre> <p>Then, following URL statement has to be written to elogd.cfg:</p> <p><code>URL = https://your.host.domain/elog</code></p> <p>There is a more detailed step-by-step instructions at the contributions section.</p>"},{"location":"adminguide.html#using-ssh","title":"Using ssh","text":"<p><code>elogd</code> can be accessed through a a SSH tunnel. To do so, open an SSH tunnel like:</p> <p><code>ssh -L 1234:your.server.name:8080 your.server.name</code></p> <p>This opens a secure tunnel from your local host, port 1234, to the server host where the <code>elogd</code> daemon is running on port 8080. Now you can access <code>http://localhost:1234</code> from your browser and reach <code>elogd</code> in a secure way.</p>"},{"location":"adminguide.html#how-it-all-works","title":"How It All Works","text":"<p>For the technically curious:</p> <p>The concept of ELOG is very simple. The logbook functionality is implemented by a single daemon program, <code>elogd</code>, which is written in C. It contains an integrated Web server, which does not serve files like standard Web servers, but reads logbook entries from its database and formats them into HTML. Since only forms and tables are used, no Java or Javascript is necessary, which makes the logbook display very fast. The system does not use any images on purpose to reduce the amount of data to be transferred. Since the ELOG daemon contains its own http server, no additional server like Apache is required.</p> <p>The \"database\" in which ELOG saves its entries is in plain ASCII format. One file is created for each day in the form <code>YYMMDDa.log</code> (where YY is the year, MM the month and DD the day). For ELOG versions 1.x.x, the format was <code>YYMMDD.log</code>. Messages are separated internally by the string <code>$@MID@$</code>. If this string is entered in a message (main body text or attribute), it gets converted automatically in order not to invalidate the database structure.</p> <p>If attachments are submitted, they are saved as separate files named <code>YYMMDD_HHMMSS_name</code> - where in addition to the date the time is specified and <code>name</code> is the original file name of the attachment. To copy the database to another computer, only the *.log files and the attachment files need to be copied. To copy for example all files from March 2001, just select them with <code>0103??a.log</code> and <code>0103??_*</code>.</p>"},{"location":"config.html","title":"ELOG - Syntax of elogd.cfg","text":"<p>Global and individual logbook options for an ELOG server</p> <p>The configuration file <code>elogd.cfg</code> contains entries which define the structure of logbooks and the behaviour of <code>elogd</code>. The file has a simple ASCII format. Each logbook is defined by a <code>[<name>]</code> section where is the name of the logbook. The <code>[global]</code> 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. <p>Here is a simple example, which define two logbooks, \"Linux\" and \"PC\":</p> <pre><code>[global]\nSMTP host = mailsend.your.domain\n\n[Linux]\nTheme = default\nComment = General linux tips and tricks\nAttributes = Author, Type, Category, Subject\nOptions Type = Routine, Software Installation, Problem Fixed, Configuration, Other\nOptions Category = General, Hardware, Software, Network, Account, Other\nOptions Author = Stefan, Linus, unknown\nRequired Attributes = Author\n\n[PC]\nComment = Database PC installations\nAttributes = Location, OS, Owner\nOptions Location = Building1, Building2\nOptions OS = Linux, Windows ME, Windows 2000\nRequired Attributes = Location, Owner\nEmail All = name@address, othername@otheraddress\nUse Mail Subject = Location\n</code></pre>"},{"location":"config.html#global-options","title":"Global options","text":"<p>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.</p> <p>If a setting has a number of possible options, they are shown in the form <code>option1|option2|...</code>, meaning that one of the options (without any vertical bar) should be used. The following options are specific to the <code>[global]</code> section:</p>"},{"location":"config.html#port-port","title":"<code>Port = <port></code>","text":"<p>Specifies the TCP port under which the server is listening. Default is 80. Can be superseeded via the '-p' command line flag.</p>"},{"location":"config.html#ssl-0-1","title":"<code>SSL = <0 | 1></code>","text":"<p>Turn on Secure Socket Layer transport. If SSL is on, one can connect via <code>https://...</code> to the elogd daemon. If the <code>URL =</code> directive is used, make sure to use <code>https://...</code> instead of <code>http://...</code> there. The ELOG distribution contains a simple self-signed certificate in the <code>ssl</code> 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 <code>0</code>.</p>"},{"location":"config.html#interface-interface","title":"<code>Interface = <interface></code>","text":"<p>Specified network interface to listen at. Can be used if several network cards are in a computer, or if one wants to restrict access to the local host only, in which case one can use 127.0.0.1 as the interface.</p>"},{"location":"config.html#resource-dir-directory","title":"<code>Resource dir = <directory></code>","text":"<p>Specifies the root directory for ELOG resources like help files, themes and icons. Can be overwritten with the <code>-s</code> flag when starting elogd. If not specified, use the directory where the configuration file <code>elogd.cfg</code> resides. Changing this option requires a restart of the elogd server.</p>"},{"location":"config.html#logbook-dir-directory","title":"<code>Logbook dir = <directory></code>","text":"<p>Specifies the root directory for logbooks. Can be overwritten with the <code>-d</code> flag when starting elogd. If not specified, use the directory where the configuration file <code>elogd.cfg</code> resides. Each logbook data is stored in a separate directory under this root directory specified by the <code>Subdir</code> option. Changing this option requires a restart of the elogd server. This directory also contains any password file and user HTML file.</p>"},{"location":"config.html#language-name","title":"<code>Language = <name></code>","text":"<p>The language setting determines the language of the <code>elogd</code> output. Not affected by this setting are the configuration file options and the commands specified with the optional <code>Menu commands</code> and <code>List menu commands</code>, 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.</p> <p>If a language name is given (currently \"german\", \"french\", \"spanish\", \"dutch\", \"brazilian\" are supported out-of-the-box), the system searches for a file named eloglang.<name> containing string translations from English into that language. If you create a new translation file, please send it back to the author to be included in future distributions.\\ \\ The online help for <code>elogd</code> 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.</p>"},{"location":"config.html#charset-name","title":"<code>charset = <name></code>","text":"<p>Specifies the charset of the pages produced by <code>elogd</code>. Can be used to switch to Russian or Asian fonts.</p>"},{"location":"config.html#logbook-tabs-01","title":"<code>Logbook Tabs = [0|1]</code>","text":"<p>This flag controls the display of \"tabs\" on top of the logbook page which allow to quickly switch between logbooks. Default is <code>1</code></p>"},{"location":"config.html#main-tab-string","title":"<code>Main Tab = <string></code>","text":"<p>If this option is present, an additional first tab is displayed which takes you back to the main logbook selection page. The <code>string</code> is used for the contents of the tab.</p>"},{"location":"config.html#main-tab-url-string","title":"<code>Main Tab URL = <string></code>","text":"<p>Normally the main tab brings one back to the logbook selection page. In case one wants to specify a different destination, such as a special web page outside of elog, one can use this statement to specify a full URL.</p>"},{"location":"config.html#welcome-title-html-code","title":"<code>Welcome Title = <html code></code>","text":"<p>This optional HTML code gets displayed in the title of the logbook selection page. It can contain images via <code><img src=\"welcome.gif\"></code>. These images must be stored in the resource directory or in the theme directory.</p> <p>The following line is an example Welcome Title:</p> <p><code>Welcome title = <img src=\"welcome.jpg\"><p><font size=5 color=white>Welcome to our Elog</font></code></p> <p>This displays an image and a text below.</p>"},{"location":"config.html#page-title-string","title":"<code>Page title = <string></code>","text":"<p>The string specified here is used for the title of individual logbook pages. It is also used by most browsers for bookmark names. <string> can contain substitutions like \\$<attribute> where <attribute> gets replaced by the attribute string from each message. The option <code>Page title</code> in the <code>[global]</code> section is used for the logbook selection page.</p>"},{"location":"config.html#list-page-title-string","title":"<code>List page title = <string></code>","text":"<p>The same for the summary or find result page. This may include substitutions as well, although attribute substitutions make no sense here, since the summary page may contain many messages with different attributes.</p>"},{"location":"config.html#selection-page-file","title":"<code>Selection page = <file></code>","text":"<p>When this option is present, a user defined file is displayed instead of the logbook selection page. This file must be stored in the resource directory. Alternatively, an absolute path can be used if the file name starts with a <code>\"/\"</code> (Unix) or <code>\"\"</code> or <code>\"x:\"</code> (Windows). It can be completely customized in order to contain logos etc. As a template, the standard selection page produced by <code>elogd</code> can be used.</p>"},{"location":"config.html#guest-selection-page-file","title":"<code>Guest Selection page = <file></code>","text":"<p>The same for installations which have a global password file. This means that the logbook selection page is also password protected. It might be however that some logbooks have guest access, in which case guest access to the selection page should be allowed as well (maybe with only a subset of the available logbooks). In that case this options can be used, to show a list of logbooks with guest access.</p>"},{"location":"config.html#protect-selection-page-0-1","title":"<code>Protect Selection page = 0 | 1</code>","text":"<p>Normally, one can see the logbook selection page without having to log in. If one wants to require a login for the selection page, this switch can be set to <code>1</code>. Default is <code>0</code>. It is necessary to put the <code>Password file = ...</code> into the [global] section of the config file for this to work.</p>"},{"location":"config.html#expand-selection-page-0-1","title":"<code>Expand Selection page = 0 | 1</code>'","text":"<p>If this option is not present or set to one, the logbook selection page is expanded (all logbooks are shown if groups of logbooks are present). If this option is zero, only the group names are displayed. If one clicks on a group, its logbooks are shown. Using this option set to zero only makes sense if one has a large number of logbooks which would not fit on a single browser window, so collapsing makes sense. Default is <code>1</code>.</p>"},{"location":"config.html#smtp-host-hostdomain","title":"<code>SMTP host = <host.domain></code>","text":"<p>This defines the SMTP host needed to send automatic email notifications. The host name you can get from your email program or your local system administrator.</p>"},{"location":"config.html#smtp-username-username","title":"<code>SMTP username = <username></code>","text":"<p>Some SMTP server require username/passowrd authentication. This option specifies the SMTP user name, while the option <code>SMTP password</code> can be created or modified via the <code>-t</code> switch when starting elogd. This is necessary since the password is encrypted. To set your SMPT password, enter on the command line:</p> <p><code>elogd -t <your password></code></p>"},{"location":"config.html#smtp-port-port","title":"<code>SMTP port = <port></code>","text":"<p>This defines the port under which the SMTP server is listening. The default is 25, but some newer servers use port 587.</p>"},{"location":"config.html#logfile-file","title":"<code>Logfile = <file></code>","text":"<p>This option specifies a filename which logs all login/logout activities and successful user connections for logbooks with user level access. The the <code>logging level</code> (see below) is larger than 1, also read and write accesses can be logged.</p>"},{"location":"config.html#logging-level-1-2-3","title":"<code>Logging level = 1 | 2 | 3</code>","text":"<p>Specifies the logging level. The higher this value, the more information is logged. Default is 2:</p> <ul> <li>1: Log only logins and logouts</li> <li>2: Log also write accesses</li> <li>3: Log also read accesses</li> </ul>"},{"location":"config.html#url-httpshostdomainportsubdir","title":"<code>URL = <http[s]://host.domain[:port]/[subdir/]></code>","text":"<p>If one of the three cases is true:</p> <ul> <li><code>elogd</code> runs with SSL enabled</li> <li><code>elogd</code> runs under a proxy</li> <li>The automatic email notifications contains the wrong URL</li> </ul> <p>then the URL under which <code>elogd</code> 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</p> URL Condition <code>URL = http://host.domain:8080/</code> if running on port 8080 <code>URL = https://host.domain/</code> if SSL is enabled (SSL = 1) <code>URL = http://host.domain/subdir/</code> if running under a proxy <p>This URL is then used for any redirection. For example if one submits a new entry, the URL in the browser reads ...<logbook>/?cmd=Submit&..., containing all the attributes etc. After the submit this page gets redirected to ...<logbook>/<ID>, where <ID> is the ID of the new entry. For the redirection via the HTTP \"Location:\" statement, an absolute URL is required. Since elogd cannot figure out the complete URL under which it is running when accessed through an Apache proxy, this statement is necessary to tell elogd the complete URL.</p>"},{"location":"config.html#relative-redirection-01","title":"<code>Relative redirection = 0|1</code>","text":"<p>Under some circumstances, absolute redirection via a complete URL may not work. If you access elogd through two different ways simulataneously, for example directly and via a stunnel connection, a single absolute URL cannot be used, because one connection starts with http://, and the other with https://. Another case is when the elogd server has a dynamic IP address, which changes from time to time. Setting <code>Relative redirection = 1</code>, 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.</p> <pre><code>Usr = <name>\nGrp = <name>\n</code></pre> <p>The user and group to run the elogd daemon under when started by root.</p>"},{"location":"config.html#resolve-host-names-01","title":"<code>Resolve host names = 0|1</code>","text":"<p>Resolve remote host names if set to 1. If set to 0, which is the default, only IP numbers are stored in any log file. If the <code>hosts allow/deny</code> 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.</p>"},{"location":"config.html#groups-of-logbooks","title":"Groups of logbooks","text":"<p>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</p> <p><code>Group <group name> = <Logbook1>, <Logbook2>, <other group></code></p> <p>in the <code>[global]</code> section of the configuration file.</p> <p>To define following logbook hierarchy:</p> <p></p> <p>one would use following statements:</p> <pre><code>[global]\nGroup Linux PCs = Red Hat, Debian, Mandrake\nGroup Windows PCs = 98, ME, NT, XP, CE\nGroup CE = 1.0, 2.0\n</code></pre> <p>The logbook tabs would then look like this:</p> <p></p> <p>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.</p>"},{"location":"config.html#top-groups","title":"Top groups","text":"<p>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 <code>Top groups</code>. The configuration could look like this:</p> <pre><code>Group Linux PCs = Red Hat, Debian, Mandrake\nGroup Windows PCs = 98, ME, NT, XP, CE\nGroup CE = 1.0, 2.UL\n\nTop group engineering = Linux PCs, Windows PCs\nTop group administration = Employees, Purchases\n\n[global engineering]\nPassword file = engineers.pwd\nAdmin user = stefan\n\n[global administration]\nPassword file = admin.pwd\nAdmin user = bill\n</code></pre> <p>Note that there can be a <code>[global]</code> 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 <code>[global <top group>]</code> setting, which by itsel overrides a setting in the <code>[global]</code> section. This way one can define settings for all top level groups (such as the SMTP host) in the <code>[global]</code> section, and define different password files and administrators in the individual top level group sections.</p> <p>If top groups are used, the root of the elogd server is not accessible any more. Presume that elogd is accessible normally under <code>http://your.host:8080/</code>, 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 <code>http://your.host:8080/engineering</code> or <code>http://your.host:8080/administration</code>. 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 <code>Show top groups = 1</code>.</p>"},{"location":"config.html#individual-logbook-options","title":"Individual logbook options","text":"<p>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 <code>[global]</code> section. Thus if the following options are placed in the <code>[global]</code> section, they are defaults for all logbooks. If they are present in the <code>[global]</code> and in the logbook section, the logbook option is used.</p> <p>Here are the available options, by broad categories:</p>"},{"location":"config.html#general-options","title":"General options","text":""},{"location":"config.html#data-dir-directory","title":"<code>Data dir = <directory></code>","text":"<p>This option is obsolete from version 2.2.5 on and should not be used. Use <code>Subdir = ...</code> instead.</p>"},{"location":"config.html#subdir-directory","title":"<code>Subdir = <directory></code>","text":"<p>Each logbook has a separate directory where the logbook entries are stored, which is controlled by this statement. If the directory does not exist, it is created autmatically by the <code>elogd</code> program. The subdirectory is relative to the logbook root directory specified with the <code>Logbook dir = ...</code> option. So if <code>Logbook dir = /usr/local/elog/logbooks</code> and <code>Subdir = Demo</code> then the logbook data is stored in <code>/user/local/elog/logbooks/Demo</code>. If the <code>Logbook dir = ...</code> option is not specified, then <code>logbooks</code> 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 <code>elogd</code> with the \"-v\" flag.</p>"},{"location":"config.html#comment-comment","title":"<code>Comment = <comment></code>","text":"<p>The comment is displayed on the logbook selection list. The selection list is displayed if more than one logbook is defined on a host and no logbook is explicitly specified in the URL.</p>"},{"location":"config.html#theme-theme","title":"<code>Theme = <theme></code>","text":"<p>A theme determines which layout and colors are used for a logbook, similar to skins in other programs. The theme option points to a subdirectory under the \"themes\" directory which resides in the resource directory. It contains all files for that theme. The format of these files is described under the Themes section.</p>"},{"location":"config.html#css-filename","title":"<code>CSS = <filename></code>","text":"<p>A given theme can contain several Cascading Style Sheets (CSS). This can be usefule if several logbooks use the same images and icons, but differnt colors. By default, the CSS elog.css is used. This statement adds an additional CSS, which can overwrite settings from elog.css. If different CSS'es should be used for different output media, this can be accomplished with a comma- separated list in the form <code>CSS = <file1>&<media1>,<file2>&<media2></code>. This will then be translated into separate style sheet statements for the different media. For example a statement <code>CSS = default.css&screen,print.css&print</code> will result in the HTML statements:</p> <pre><code> <link rel=\"stylesheet\" type=\"text/css\" href=\"default.css\" media=\"screen\">\n <link rel=\"stylesheet\" type=\"text/css\" href=\"print.css\" media=\"print\">\n</code></pre>"},{"location":"config.html#title-image-string","title":"<code>Title image = <string></code>","text":"<p>HTML code for the icon in the upper right corner. By default, following code is used:</p> <p><img border=0 src=\"elog.gif\" alt=\"ELOG logo\"></p> <p>This code can be replaced by <code><string></code> 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 <code><elog root>/themes/default</code>.</p>"},{"location":"config.html#title-image-url-url","title":"<code>Title image URL = <URL></code>","text":"<p>The ELOG icon at the right upper corner usually points to the ELOG home page. This URL can be changed to point to a corporate page for example with this option. The icon can be changed by replacing the <code>elog.gif</code> icon in the theme directory. This option should only be used if the <code>Title image</code> option is not used.</p>"},{"location":"config.html#time-format-string","title":"<code>Time format = <string></code>","text":"<p>This option determines how the date and time of a logbook entry is displayed. The format of the string is the same as the C function strftime, so a string of %A, %B %d, %Y, %H:%M yields in a display of Thursday, November 15, 2001, 12:35 for example.</p>"},{"location":"config.html#time-format-attribute-string","title":"<code>Time format <attribute> = <string></code>","text":"<p>Same, but just for an individual attribute.</p>"},{"location":"config.html#date-format-string","title":"<code>Date format = <string></code>","text":"<p>This option determines how the date is displayed from attributes which are of type \"date\". The format of the string is the same as the C function strftime, so a string of %A, %B %d, %Y yields in a display of Thursday, November 15, 2001 for example.</p>"},{"location":"config.html#date-format-attribute-string","title":"<code>Date format <attribute> = <string></code>","text":"<p>Same, but just for an individual attribute.</p>"},{"location":"config.html#welcome-page-file","title":"<code>Welcome Page = <file></code>","text":"<p>By default, the list with the last twenty entries of a logbook is displayed when the logbook is selected. This can be overridden with this option, which causes a HTML file to be shown instead of the message list. This file can contain further links for new logbook messages of for logbook queries. Here is a simple example of such a file:</p> <pre><code><h1>Welcome to the test logbook</h1>\n<ul>\n <li><a href=\"?cmd=new\">Enter</a> a new message\n `<li><a href=\"?cmd=find\">Search</a> the logbook\n</ul>\n</code></pre> <p>The file must be present in the resource directory. Alternatively, an absolute path can be used if the file name starts with a <code>\"/\"</code> (Unix) or <code>\"\"</code> or <code>\"x:\"</code> (Windows).</p>"},{"location":"config.html#start-page-command","title":"<code>Start page = <command></code>","text":"<p>This option can be used to display a different start page. <code>command</code> can be either 0?cmd=Last to display the last message, or any other ELog menu command in the form <code>?cmd=xxx</code>. To start with the search page, one uses</p> <p><code>Start page = ?cmd=Find</code></p> <p>Please 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).</p>"},{"location":"config.html#submit-page-file","title":"<code>Submit Page = <file></code>","text":"<p>This optional page can be displayed when a new message was submitted in a logbook. Here is an example:</p> <pre><code><h1>You successfully submitted a message</h1>\n<a href=\"?cmd=Back\">Back</a> to the logbook<p>\n<a href=\"?cmd=New\">Enter</a> another message\n</code></pre> <p>The file must be present in the logbook directory. Alternatively, an absolute path can be used if the file name starts with a <code>\"/\"</code> (Unix) or <code>\"\"</code> or <code>\"x:\"</code> (Windows).</p>"},{"location":"config.html#message-comment-comment","title":"<code>Message comment = <comment></code>","text":"<p>This optional comment is displayed on top of the text entry field when submitting a new message. It can contain a sentence like \"Please enter your message here:\".</p>"},{"location":"config.html#reply-comment-comment","title":"<code>Reply comment = <comment></code>","text":"<p>This optional comment is displayed on top of the text entry field when replying to an exiting entry. It can contain a sentence like \"Please enter your reply here:\".</p>"},{"location":"config.html#attachment-comment-comment","title":"<code>Attachment comment = <comment></code>","text":"<p>This optional comment is displayed on top of the attachment sumbission section when entering a new message. It can contain a sentence like \"Please upload your attachments here:\".</p>"},{"location":"config.html#menu-commands-list","title":"<code>Menu commands = <list></code>","text":"<p>This option specifies the menu commands displayed on top of a single logbook page. For certain installations, it can be useful to disable some commands. Following commands are possible:</p> <ul> <li>New - Enter new logbook entry</li> <li>Edit - Edit current logbook entry</li> <li>Delete - Delete current logbook entry</li> <li>Reply - Submit a reply to current entry</li> <li>Duplicate - Duplicate the current entry with the possibility to change some values</li> <li>Download - Download a message in ASCII format</li> <li>Find - Search entries in logbooks</li> <li>Last day - Display entries from last day</li> <li>Move to - Move entry to other logbook</li> <li>Copy to - Copy entry to other logbook</li> <li>Config - Edit elogd.cfg (if no \"Password file\" is given)</li> <li>Config - Modify/Add user accounts (if \"Password file\" is given)</li> <li>Admin - Edit elogd.cfg (if \"Password file\" is given)</li> <li>Login - Login with user name and password (if \"Password file\" is given)</li> <li>Import - Show CSV (comma-separated-values) import page</li> <li>Logout - Logout current user (if \"Password file\" is given)</li> <li>Help - General help</li> </ul> <p>The commands are always in English, independent of the <code>language = ...</code> setting, and are automatically translated into the specified language.</p> <p>If this option is not present, following default is used:</p> <p><code>Menu commands = List, New, Edit, Delete, Reply, Duplicate, Find, Config, Help</code></p>"},{"location":"config.html#copy-to-logbook-list","title":"<code>Copy to = <logbook list></code>","text":""},{"location":"config.html#move-to-logbook-list","title":"<code>Move to = <logbook list></code>","text":"<p>The commands <code>Copy to</code> and <code>Move to</code> 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 <code>Copy to = <logbook list></code> and <code>Move to = <logbook list></code> 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 <code>Preserve IDs</code> can be used to keep the entry ID in the destination logbook.</p>"},{"location":"config.html#list-menu-commands-list","title":"<code>List Menu commands = <list></code>","text":"<p>This option specifies the menu commands displayed on top of the listing page. Although all commands from a above are possible, only the commands <code>New, Find, Select, Import, Config, Admin, Change password, Logout</code> and <code>Help</code> make sense. The command <code>Select</code> can be used to select multiple messages for deletion or for moving to other logbooks. Once the <code>Select</code> 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 <code>Delete</code> and optionally a <code>Coyp to ...</code> and <code>Move to ...</code> button, if these commands are present in the <code>Menu commands</code> list. Pressing one of these buttons deletes, copies or moves all selected logbook entries.</p>"},{"location":"config.html#guest-menu-commands-list","title":"<code>Guest Menu commands = <list></code>","text":"<p>This option specifies the menu commands for guest logins. A guest login happens if a password file is used, but someone accesses the logbook for the first time, which means that no username/password is given. In that case the commands from the guest menu are displayed, which usually contain a subset of the normal commands. A typical scenario is a logbook which only has commands to read the logbook on the guest menu, but no commands to write/edit entries. Instead, the login command is given in the guest menu, with which one can login as a real user (username and password have to match those from the password file), which then allowes full access via the \"Menu commands\" list. A typical example for the menu settings for this scenario are:</p> <pre><code> Menu commands = List, New, Edit, Reply, Duplicate, Find, Config, Logout, Help\n Guest menu commands = List, Find, Login, Help\n</code></pre> <p>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 <code>Guest menu commands</code> option with the following <code>Guest List Menu commands</code> option to restrict the access to the find result page as well.</p>"},{"location":"config.html#guest-list-menu-commands-list","title":"<code>Guest List Menu commands = <list></code>","text":"<p>Same as Guest Menu commands but for the find result page.</p>"},{"location":"config.html#menu-text-file","title":"<code>Menu text = <file></code>","text":"<p>If this option is present, and additional menu row above the message gets displayed with the contents of <file>. This file can contain arbitrary text, images or links. One example would be following text to go back to the listing page and display the next Routine entry and all Routine entries:</p> <pre><code><small>\n&nbsp;<a href=\"?cmd=next&type=Routine\">Next Routine entry</a>&nbsp;|\n&nbsp;<a href=\"../?Type=Routine\">All Routine entries</a>\n</small>\n</code></pre>"},{"location":"config.html#list-menu-text-file","title":"<code>List Menu text = <file></code>","text":"<p>The same for the list page.</p>"},{"location":"config.html#filter-menu-text-file","title":"<code>Filter Menu text = <file></code>","text":"<p>The same for the filter line in the list page.</p>"},{"location":"config.html#guest-display-list","title":"<code>Guest Display = <list></code>","text":"<p>This option specifies which attributes are displayed on guest access. It is possible to display only a subset of all attributes for guest access, but the full list if someone is logged in (using the option \"Password file\"). The <code>list</code> consists of comma separated attributes, including the word text, if one wants to display the entry body text for guests.</p> <pre><code><small>\n&nbsp;<a href=\"?mode=summary\">Summary</a>&nbsp;|\n&nbsp;<a href=\"?mode=full\">Full</a>&nbsp;|\n&nbsp;<a href=\"?mode=threaded\">Threaded</a>&nbsp;|\n</small>\n</code></pre>"},{"location":"config.html#top-text-file-string","title":"<code>Top text = <file> | <string></code>","text":"<p>The text of this option gets displayed at the top of every Elog page. It can be a string or a filename which gets displayed. Might be useful to display company logos etc. 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 <code>\"/\"</code> (Unix) or <code>\"\"</code> or <code>\"x:\"</code> (Windows).</p>"},{"location":"config.html#bottom-text-file-string","title":"<code>Bottom text = <file> | <string></code>","text":"<p>The text of this option gets displayed at the bottom of every Elog page instead of the little Elog home page link. It can be a string or a file. It can contain for example a link back to the main logbook selection page like:</p> <p><code><center><a href=\"/\">Main page</a></center></code></p> <p>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 <code>\"/\"</code> (Unix) or <code>\"\"</code> or <code>\"x:\"</code> (Windows).</p>"},{"location":"config.html#bottom-text-login-file-string","title":"<code>Bottom text login = <file> | <string></code>","text":"<p>The same as <code>Bottom text</code> 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.</p>"},{"location":"config.html#help-url-url","title":"<code>Help URL = <URL></code>","text":"<p>This URL is used for the Help button. By default, the file eloghelp_xx.html is returned with the contents of the help page. Edit this file directly to add site-specific help for all logbooks. Alternatively, use the <code>Help URL</code> option to specify different help pages for different logbooks. It can point to a site-specific help page via <code>http://...</code> or to a local file like <code>file://c:/tmp/config.html</code>, or to the name of an HTML file which must be present in the resource directory.</p>"},{"location":"config.html#message-width-number","title":"<code>Message Width = <number></code>","text":"<p>This value sets the number of characters per line of the main message entry field. The default value is 76 (78 for replies), and can be increased for installations which need a larger window size (like pasting log files etc.). If both <code>Message Width</code> and <code>Message Height</code> are not given, some JavaScript code is used which automatically resizes the message window dynamically to fit optimally into the browser window.</p>"},{"location":"config.html#message-height-number","title":"<code>Message Height = <number></code>","text":"<p>This value sets the number of lines of the main message entry field. The default value is 20, and can be changed for installations which need a different window size. If both <code>Message Width</code> and <code>Message Height</code> are not given, some JavaScript code is used which automatically resizes the message window dynamically to fit optimally into the browser window.</p>"},{"location":"config.html#admin-textarea-colsrows","title":"<code>Admin textarea = <cols>,<rows></code>","text":"<p>This defines the textarea size for the admin page. Default is 80,40.</p>"},{"location":"config.html#display-mode-fullsummarythreaded","title":"<code>Display mode = [full|summary|threaded]</code>","text":"<p>Default mode for search display. On the find entry form, the checkboxes are set accordingly. The \"Last xxx\" page uses this setting directly.</p>"},{"location":"config.html#entries-per-page-number","title":"<code>Entries per page = <number></code>","text":"<p>Number of logbook entries displayed per page in a search result. The default is 20.</p>"},{"location":"config.html#restrict-edit-time-hours","title":"<code>Restrict edit time = <hours></code>","text":"<p>If this option is set, a new message can only be edited a certain number of hours after its creation. This can be useful if one wants to ensure that old entries cannot be modified. Hours can also be fractional, like 0.5 for 30 min.</p>"},{"location":"config.html#admin-restrict-edit-time-hours","title":"<code>Admin restrict edit time = <hours></code>","text":"<p>Same option for admin users. This can be useful if normal users are not allowed to change entries after \"restrict edit time\", but an admin user should be allowed to do so. Setting this to zero disables any restriction for admin users and they can edit entries forever.</p>"},{"location":"config.html#max-content-length-bytes","title":"<code>Max content length = <bytes></code>","text":"<p>This option restricts the size of attachments. When very large (>100MB) attachments are uploaded, the elogd server can be busy with this upload for a longer time and not respond to other requests during that time. To avoid this, the maximum size of attachments can be restricted. The server will then refuse to accept larger attachments. The default is 10485760 (= 10 MB). This option has to be placed into the [global] section and the elogd server has to be restarted after a change.</p>"},{"location":"config.html#fonts-list","title":"<code>Fonts = <list></code>","text":"<p>List of fonts (comma separated) to be shown in the font drop-down box of the entry edit form. Default is</p> <p><code>Fonts = Arial, Comic Sans MS, Courier New, Tahoma, Times New Roman, Verdana</code></p> <p>On Unix systems some of these fonts might not be installed, in which case they can be replaced by others like Serif, Sans-serif, Helvetica.</p>"},{"location":"config.html#all-display-limit-n","title":"<code>All display limit = <n></code>","text":"<p>If a logbook contains many entries, the list gets divided into pages, with some page navigation for the next, previous, a specific page and all pages. If the logbook contains a large number of entries (>500), the display of all thes entries can take very long and might slow down the elogd server, especially if the entries are not displayed in \"summary\" mode but in \"full\" mode. Therefore the \"All\" link should not be used in the page navigation for large logbooks. The number of entries from when on the \"All\" link gets hidden can be specified with this number, the default value is <code>500</code>.</p>"},{"location":"config.html#thumbnail-size-size","title":"<code>Thumbnail size = <size></code>","text":"<p>This option determines the default thumbnail size. To make the automatic generation of thumbnails working, the ImageMagick package has to be installed. Refer to the admin guide for installation instructions. The thumbnail size <code>size</code> gets passed to the <code>-thumbnail</code> option of the conversion. A value of <code>300</code> converts all pictures to thumbnails 300 pixels wide. A value of <code>300></code> 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 <code>10%</code> 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:</p> <p></p> <p>Setting <code>Thumbnail size = 0</code> turns off the thumbnail creation.</p>"},{"location":"config.html#thumbnail-options-options","title":"<code>Thumbnail options = <options></code>","text":"<p>With this option one can pass additional parameters to the ImageMagick package. They are passes 1:1 to the convert program. Commonly used is the -density option to increase the image quality when converting from PDF or EPS files.</p>"},{"location":"config.html#attributes","title":"Attributes","text":""},{"location":"config.html#attributes-list","title":"<code>Attributes = <list></code>","text":"<p>Define a number of attributes for the logbook, separated by commata. A maximum of 100 attributes can be defined. Typical values are \"Author\", \"Subject\" or \"Type\". Following values are not allowed:</p> <ul> <li>Text</li> <li>Date</li> <li>Encoding</li> <li>Reply to</li> <li>In reply to</li> <li>Locked by</li> <li>Attachment</li> <li>Path</li> </ul> <p>since these are used internally by elog.</p>"},{"location":"config.html#options-attribute-list","title":"<code>Options <attribute> = <list></code>","text":"<p>Usually, an text field is used for an attribute, where the user can fill in text of up to 100 characters. If instead a drop-down box with preset items is better for a given attribute, these items can be defined with this statement. Up to 100 items can be defined, separated by commas. To add an option including a comma, encose it in quotations marks like</p> <p><code>Options town = San Francisco, \"Paris, Texas\", \"Paris, France\"</code></p>"},{"location":"config.html#extendable-options-list","title":"<code>Extendable options = <list></code>","text":"<p>When using the <code>Options <attribute></code> 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 <code>Extandable options</code> 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 automatically appears in the drop-down box for that attribute.</p>"},{"location":"config.html#roptions-attribute-list","title":"<code>ROptions <attribute> = <list></code>","text":"<p>Same as <code>Options</code> above, but using radio buttons instead of a drop-down box.</p>"},{"location":"config.html#moptions-attribute-list","title":"<code>MOptions <attribute> = <list></code>","text":"<p>This list allows for \"Multiple Options\", meaning that an attribute can have several values simultaneously. When entering an entry with MOptions, each value from the list is represented by a checkbox. Unlike with normal options, multiple checkboxes can be checked for an entry. The attribue value then becomes</p> <p><code><value1> | <value2> | ...</code></p> <p>In the \"find\" page only one of these values can be specified, which is then treated as a substring in the search filter.</p>"},{"location":"config.html#ioptions-attribute-list","title":"<code>IOptions <attribute> = <list></code>","text":"<p>This list specifies a set of icons for an attribute. Some icons are contained in the themes/default/icons directory which can be used here like</p> <pre><code>Attributes = Author, Icon, Subject...\nIOptions Icon = icon1.gif, icon2.gif, icon3.gif, ...\n</code></pre> <p>New icons are welcome and should be sent back to the author to be incorporated in the next version.</p>"},{"location":"config.html#comment-attribute-comment","title":"<code>Comment <attribute> = <comment></code>","text":"<p>Optional comment which is displayed below the attribute name in the entry form. Can be used to explain the attribute somehow.</p>"},{"location":"config.html#tooltip-attribute-comment","title":"<code>Tooltip <attribute> = <comment></code>","text":"<p>Same as <code>Comment <attribute></code>, except that the comment gets displayed as a tooltip (tiny pup-up window) when the user moves the mouse cursor over the attribute name in the entry form.</p>"},{"location":"config.html#tooltip-attribute-attribute-option-comment","title":"<code>Tooltip <attribute> <attribute option> = <comment></code>","text":"<p>Same as <code>Tooltip <attribute></code>, but for option values of a <code>MOptions</code> attribute. Using this option, a different tooltip can be shown above each check box of an optional value for an attribute. Please note that attributes or options with spaces should not be enclosed with quotes.</p>"},{"location":"config.html#icon-comment-icon-comment","title":"<code>Icon comment <icon> = <comment></code>","text":"<p>Icons may contain a comment, which is then used in email notifications instead of the icon file name. One has to add a separate icon comment for each icon file.</p>"},{"location":"config.html#options-attribute-boolean","title":"<code>Options <attribute> = boolean</code>","text":"<p>If an attribute is marked \"boolean\" this way, a checkbox is displayed for this attribute.</p>"},{"location":"config.html#preset-attribute-string","title":"<code>Preset <attribute> = <string></code>","text":"<p>This option uses a preset string for an attribute. The string can contain subsitutions like the ones described under the \"Subst <attribute>\" command. One possible application is to use the login name for the author field like:</p> <p><code>Preset Author = $long_name</code></p> <p>If the attribute should be locked at the Web submission, use the \"Locked Attributes = ...\" option. If a preset value is given for an attribute which has an options list, the preset value is selected in the drop down box by default.</p>"},{"location":"config.html#preset-text-string-or-file","title":"<code>Preset text = <string> or <file></code>","text":"<p>This preset value is used for the main body text. It can be a string or a file, which must be present in the logbook directory. Alternatively, an absolute path can be used if the file name starts with a <code>\"/\"</code> (Unix) or <code>\"\"</code> or <code>\"x:\"</code> (Windows).</p>"},{"location":"config.html#preset-on-edit-attribute-string","title":"<code>Preset on edit <attribute> = <string></code>","text":"<p>Same as <code>Preset <attribute></code>, but evaluated when editing existing entries.</p>"},{"location":"config.html#preset-on-reply-attribute-string","title":"<code>Preset on reply <attribute> = <string></code>","text":"<p>Same as <code>Preset <attribute></code>, but evaluated for replies.</p>"},{"location":"config.html#preset-on-first-reply-attribute-string","title":"<code>Preset on first reply <attribute> = <string></code>","text":"<p>While <code>Preset on reply <attribute></code>, is evaluated for any replies, this one is only executed for the first reply to an entry. It can be useful for example to so do something like this:</p> <p><code>Preset on first reply Subject = Re: $Subject</code></p> <p>So the \"Re:\" only gets added once, and you don't get long chains of \"Re: Re: Re: ....\".</p>"},{"location":"config.html#preset-on-duplicate-attribute-string","title":"<code>Preset on duplicate <attribute> = <string></code>","text":"<p>Same as <code>Preset <attribute></code>, but evaluated for duplicted entries.</p>"},{"location":"config.html#locked-attributes-list","title":"<code>Locked Attributes = <list></code>","text":"<p>The attributes specified here cannot be modified when a new entry is submitted. This makes only sense for preset attributes.</p>"},{"location":"config.html#fixed-attributes-edit-list","title":"<code>Fixed Attributes Edit = <list></code>","text":"<p>The attributes specified here cannot be modified when an existing entry is modified via the <code>Edit</code> button. This feature can be useful to preserve the original author of the message, when using the <code>Preset Author = $long_name</code> option as described above.</p>"},{"location":"config.html#fixed-attributes-reply-list","title":"<code>Fixed Attributes Reply = <list></code>","text":"<p>The attributes specified here cannot be modified when an existing entry is replied on via the <code>Reply</code> button. This feature can be useful to preserve the original subject of a message for example.</p>"},{"location":"config.html#required-attributes-list","title":"<code>Required Attributes = <list></code>","text":"<p>The attributes specified here are required when a new entry is submitted. The attribute names are marked with * on the entry form.</p>"},{"location":"config.html#show-attributes-list","title":"<code>Show Attributes = <list></code>","text":"<p>Attributes present in this list are shown in the single entry page. Omitting attributes can make sense for attributes which are automatically derived from other attributes via the <code>Change <attribute></code> command.</p>"},{"location":"config.html#show-attributes-edit-list","title":"<code>Show Attributes Edit = <list></code>","text":"<p>The same as <code>Show Attributes</code>, but for the entry form.</p>"},{"location":"config.html#propagate-attributes-list","title":"<code>Propagate Attributes = <list></code>","text":"<p>With this option, changed in an attribute are autmatically propagated to all entries of a thread. This can be useful if one has an attribute \"problem status\" for example with the options \"open\", \"under investigation\", \"fixed\". A thread related to a specific problem can then have several replies. If the problem gets fixed, a new reply can be made with the attribute \"problem status\" being \"fixed\", and then the propagation causes all entries of this thread to become \"fixed\".</p>"},{"location":"config.html#page-title-string_1","title":"<code>Page title = <string></code>","text":"<p>The string specified here is used for the title of the web page. It is also used by most browsers for bookmark names. The string can contain substitutions as described unter the \"Subst <attribute>\" option.</p>"},{"location":"config.html#edit-page-title-string","title":"<code>Edit Page title = <string></code>","text":"<p>The string specified here is used for the title of the entry form. It is also used by most browsers for bookmark names. The string can contain substitutions as described unter the \"Subst <attribute>\" option.</p>"},{"location":"config.html#list-display-list","title":"<code>List display = <list></code>","text":"<p>Specified the display and order of items in a message listing page or a search result page. In addition to all attributes, following items can be specified:</p> <ul> <li><code>ID</code> for the entry ID</li> <li><code>Date</code> for the entry date/time</li> <li><code>Edit</code> to display a column with an edit icon to directly edit and entry</li> <li><code>Delete</code> to display a column with a delete icon to directly delete and entry</li> </ul> <p>The restriction to certain attributes can be helpful if many attributes are defined in a logbook, which usually makes the table too big to fit in the browser. The default is\\</p> <p><code>List display = ID, Date, <all attributs></code></p> <p>Which displays the message number, date, and all attributes. The display of the message body is controlled by the <code>Display mode</code> and <code>Summary lines</code> options. If a search goes over \"all logbooks\", an additional colums with the logbook name of each entry is added in front.</p>"},{"location":"config.html#guest-list-display-list","title":"<code>Guest List display = <list></code>","text":"<p>Same as <code>List display</code>, but for guest access (user level access with password, but not logged in). Please see also <code>Guest display</code>. In addition to <code>List display</code>, one can optionally specify <code>Text</code> as an attribute here. Without that attribute, the summary text of the entry body is not shown. This makes it possible to show the text for registered users and hide it for guest access.</p>"},{"location":"config.html#link-display-list","title":"<code>Link display = <list></code>","text":"<p>Normally, each column in the display list contains a link to the individual entry. If this is not desired, the list of attributes with links can be restricted to only a subset with this option.</p>"},{"location":"config.html#thread-display-string","title":"<code>Thread display = <string></code>","text":"<p>Optional way to specify the line contents in the threaded search result. Following substitutions are possible:</p> <ul> <li>$<attribute>**: The value of the attribute</li> <li>$logbook**: The name of the current logbook</li> <li>$entry time: The message date and time, formatted via \"Time format\"</li> <li>$message id**: The message ID</li> </ul> <p>A typical example would be</p> <p><code>Thread display = $subject, posted by $author on $entry time</code></p>"},{"location":"config.html#thread-icon-attribute","title":"<code>Thread icon = <attribute></code>","text":"<p>If a logbook uses some icons for an attribute, these icons can be displayed in the search result page instead of the default icons contained in the themes directory.</p>"},{"location":"config.html#rss-title-string","title":"<code>RSS Title = <string></code>","text":"<p>ELOG supports so-called RSS feeds. Once can subscribe to new logbook entries with RSS readers such as Mozilla Firefox. Once new entries are submitted to the logbook, the become visible in the subscripition. By default, all attributes of the last 15 logbook entries are used as the RSS title. With this option once can changed this behaviour. Following substitutions are possible:</p> <ul> <li>$<attribute>: The value of the attribute</li> <li>$logbook: The name of the current logbook</li> <li>$entry time: The message date and time, formatted via \"Time format\"</li> <li>$message id: The message ID</li> </ul> <p>A typical example would be\\</p> <p><code>RSS Title = $subject, posted by $author on $entry time</code></p>"},{"location":"config.html#rss-entries-n","title":"<code>RSS Entries = <n></code>","text":"<p>Number of entries to be shown in the RSS feed. Default is 15.</p>"},{"location":"config.html#subst-attribute-string","title":"<code>Subst <attribute> = <string></code>","text":"<p>When submitting logbook entries, attribute values can be substituted by some text. This text can contain arbitrary fixed text and following values:</p> <ul> <li>$<attribute>: The entered value of the attribute itself</li> <li>$host: The host name where <code>elogd</code> is running</li> <li>$remote_host: The host name of the host from with the entry was submitted</li> <li>$short_name: The login name (if password file is present)</li> <li>$long_name: The full name from the password file for the current user</li> <li>$user_email: The email address from the password file for the current user</li> <li>$logbook: The name of the current logbook</li> <li>$date: The current date, formatted via \"Date format\"</li> <li>$utcdate: The current UTC date (GMT) and time, formatted via \"Date format\"</li> <li>$version: The version of the ELOG server in the form x.y.z</li> <li>$revision: The Subversion reversion of the ELOG server as an integer number</li> <li>$shell(<command>): <command> gets passed to the operating system shell and the result is taken for substitution.</li> </ul> <p>Following example use this feature to add the remote host name to the author:\\</p> <p><code>Subst Author = $author from $remote_host</code></p> <p>Following example substitutes an attribute with the contents of a file:</p> <pre><code>Subst Info = $shell(cat /tmp/filename) (Unix)\nSubst Info = $shell(type c:\\tmp\\filename) (Windows)\n</code></pre> <p>A special option are automatically generated tags, which are automatically incremented for each new message. This is achieved by putting #'s into the substitution string, which is used as a placeholder for the incrementing index. Each \"#\" stands for one digit, thus the statement</p> <p><code>Subst Number = XYZ-#####</code></p> <p>results in automatically created attributes \"Number\" of the form</p> <pre><code>XYZ-00001\nXYZ-00002\nXYZ-00003\n</code></pre> <p>and so on. In addition to the #'s one may specify format specifiers which are passed to the strftime function. This allows to create tags wich contain the current year, month and so on. Once the date part of the attribute changes, the index restarts from one. The statement</p> <p><code>Subst Number = XYZ-%Y-%b-###</code></p> <p>results in automatically created attributes \"Number\" of the form</p> <pre><code>XYZ-2005-Oct-001\nXYZ-2005-Oct-002\nXYZ-2005-Oct-003\n</code></pre> <p>and</p> <pre><code>XYZ-2005-Nov-001\nXYZ-2005-Nov-002\n</code></pre> <p>on the next month.</p>"},{"location":"config.html#remove-on-reply-list","title":"<code>Remove on reply = <list></code>","text":"<p>This option clears one or more (separated by commata) attribute values from a logbook entry when creating a reply to that entry. This can make sense for example for the author, since the author of a reply can be different from the original author.</p>"},{"location":"config.html#quote-on-reply-0-1","title":"<code>Quote on reply = 0 | 1</code>","text":"<p>This flag controls if the original text is quoted in a reply. Default is 1</p>"},{"location":"config.html#reply-string-string","title":"<code>Reply string = <string></code>","text":"<p>String used to mark original message lines. Default is <code>\"> \"</code>. Can be empty string (\"\") if no message marking is desired.</p>"},{"location":"config.html#subst-on-reply-attribute-string","title":"<code>Subst on reply <attribute > = <string></code>","text":"<p>Substitution of attributes for replies. This option can be used to replace the current subject with a \"Re: <old subject>\":\\</p> <p><code>Subst on reply subject = Re: $subject</code></p> <p>Note that this option works only for the first reply. So a reply-to-a-reply would still have Re: <old subject> and not Re: Re: <old subject>. If you want the substitution for all replies, please use <code>Preset on reply</code> instead.</p>"},{"location":"config.html#subst-on-edit-attribute-string","title":"<code>Subst on edit <attribute > = <string></code>","text":"<p>Substitution of attributes for edited messages. This option can be used to replace the author by the current author for example:\\</p> <p><code>Subst on edit author = $full_name</code></p>"},{"location":"config.html#quick-filter-list","title":"<code>Quick filter = <list></code>","text":"<p>Specifies list of comma separated attributes for which a drop-down filter is displayed in the search result page. By selecting a value from that drop-down box, only entries with that value are displayed. In addition to all attributes defined in the <code>Attributes =</code> list, the attribute <code>Date</code> and the option <code>Subtext</code> can be listed here. Using the <code>Date</code> filter, the last day, week, month and so on can be displayed. The <code>Subtext</code> filter works on the entry body text.</p>"},{"location":"config.html#last-default-n","title":"<code>Last default = <n></code>","text":"<p>Some logbooks are very big and searching through all entries with a quick filter can be time consuming. This option sets a default value for the <code>Date</code> quick filter, so that by default only the <n> last days are displayed. <n> has to match one of the entries of the data quick filter options, which are 1, 3, 7, 31, 92, 182, 364.</p>"},{"location":"config.html#format-attribute-flagscss_class_namecss_class_valuewidthsize","title":"<code>Format <attribute> = <flags>,<css_class_name>,<css_class_value>,<width>,<size></code>","text":"<p>Optional formatting parameters for attributes. Following items can be defined in the comma-separated list:</p> <p>Values used for single message display page:</p> <ul> <li><flags> Sum of following flags:<ul> <li>1: Display attribute in same line as previous attribute</li> <li>2: Display radio buttons or check boxes in separate lines (if applicable)</li> </ul> </li> <li><css_class_name>,<css_class_value> Cascading Style Sheet class names used for cells containing attribute name or value, respectively. The classes must be defined in the style sheet file (usually themes/default/default.css).</li> </ul> <p>Values used for new message entry form:</p> <ul> <li><width> Width of the text entry field in characters</li> <li><size> Maximum number of characters allowed.</li> </ul> <p>Default is \"0, attribname, attribvalue, 80, 500\". Trailing parameters can be ommitted, so specifying for example only the flags is possible.</p>"},{"location":"config.html#type-attribute-date-datetime-numeric-userlist-useremail-muserlist-museremail","title":"<code>Type <attribute> = date | datetime | numeric | userlist | useremail | muserlist | museremail</code>","text":"<p>A normal attribute can contain strings of any type. With this option, attributes can be forced to be numeric or to be a date/time, or to consist of a list of all users from the password file. When new logbook entries are made, numeric attributes are checked to contain only digits. Note that JavaScript has to be enabled to do this.</p> <p>Attributes of type <code>date</code> are treated as a date. Their format for display can be controlled by the <code>Date format</code> option. Upon entry, drop-down boxes are displayed which let the user select the day, month and year. Alternatively, a pop-up date picker using a calendar can be displayed if JavaScript is enabled. Date attributes are saved internally as seconds since 1.1.1970, and can therefore be sorted propoerly by clicking on the header of a logbook entry list. On the find page, dates can be searched for via a start and end date. If date attributes are used in a quick filter (see above), a drop-down quick filter box is displayed which lets the user select \"last day\", \"last week\", \"next week\", and so on. The <code>datetime</code> type combines a date and time in HH:MM. The output of this combination is controlled by the <code>Time format</code> option.</p> <p>If the attribute type is <code>userlist</code>, a drop-down box is displayed which contains all user names from the current password file. This can be useful for example in a bug tracking system, where a new entry gets assigned to an individual. The type <code>useremail</code> is similar, just a list of email addresses of all registered users. This can be used to send email notification to assigned people by using this attribute in an <code>Email all = <attribute></code> statement. The type <code>muserlist</code> and <code>museremail</code> are the same that <code>userlist</code> and <code>useremail</code>, except that several user names or user emails can be selected at once using check boxes.</p>"},{"location":"config.html#style-attribute-value-style","title":"<code>Style <attribute> <value> = <style></code>","text":"<p>Optional formatting of logbok entries in list mode. For some logbooks it might be useful to display different entries in a different color for example. To achieve this, a CSS style sheet can be attached to an entry based on the value of an attribute. If you have an attribute called <code>importnace</code> and you want to highlight all entries where <code>importnace</code> is <code>severe</code> for example, you can specify following style:</p> <p><code>Style importance severe = background-color:red</code> </p> <p>For possible formattings, please refer to some CSS documentation. You can change the colors, font styles and sizes. The style is then valid for the whole row of that entry.</p> <p>For empty attributes one can specify \"\", such as</p> <p><code>Style importance \"\" = background-color:red</code></p>"},{"location":"config.html#cell-style-attribute-value-style","title":"<code>Cell Style <attribute> <value> = <style></code>","text":"<p>Same as above, but only for a specific cell containing <attribute>. Following options</p> <pre><code>Attributes = Author, Status\nOptions Status = Fixed, Under Process, Not Fixed\nCell Style Status Fixed = background-color:green\nCell Style Status Not Fixed = background-color:red\nCell Style Status Under Process = background-color:yellow\n</code></pre> <p>for example produce following listing:</p> <p></p>"},{"location":"config.html#change-attribute-string","title":"<code>Change <attribute> = <string></code>","text":"<p>Instead of subsituting an attribute, the original attribute can be kept and just the output formatting can be changed. This can be very handy for constructing HTML links out of attributes. Presume that a company has a telephone book reachable under</p> <p><code>http://any.company.com/telbook.cgi?search=<name></code></p> <p>where <name> has to be replaced by a search string. Now one can construct an automatic telephonebook lookup with following options:\\</p> <pre><code>Attributes = Name, Telephone, ...\nChange Telephone = <a href=\"http://any.company.com/telbook.cgi?search=$Name\">$Name's telephone number</a>\n</code></pre> <p>The attribute <code>Telephone</code> is now automatically constructed from the attribute <code>Name</code> and consists of a link to the company's telephonebook. The advantage of this system is if the URL of the telephonebook changes one day, only one statement in the config file has to be changed, while otherways (like with the <code>Subst Telephone = ...</code> option) all entries would have to be changed manually.</p>"},{"location":"config.html#list-change-attribute-string","title":"<code>List Change <attribute> = <string></code>","text":"<p>Same option for the list display.</p>"},{"location":"config.html#execute-new-edit-delete-command","title":"<code>Execute new | edit | delete = <command></code>","text":"<p>It is possible to execute a shell command on the server side after a new message has been submitted, edited or deleted. This feature has been used in the past for SMS notifications over a telephone system and for synchrnonization of the ELOG database with an external SQL database. The <code><command></code> can contain substitutions similar to the <code>Subst</code> command. In addition the list of all attachments can be referred to via <code>$<attachments></code>. The text body of the entry can be referred to with <code>$text</code>. It should be noted that only the first 1500 characters of the text can be used, in order not to exceed the limits of the shell. Following (Unix) command writes a notification into some file:</p> <p><code>Execute new = echo \"New message wiht ID $message id of type $type from $long_name on $remote_host\" >> /tmp/elog.log</code></p> <p>It should be noted that this feature can impose a security problem. If someone can edit the elogd.cfg through the <code>Config</code> command of elogd, that person can put malicious code into elogd.cfg and execute it. This is even more severe if elogd runs with root privileges. To avoid such problems, the execute facility is disabled in elogd by default and has to be enabled explicitly with the \"-x\" command line flag. The administrator has to ensure then of course that only trusted people can edit elogd.cfg.</p>"},{"location":"config.html#last-submission-string","title":"<code>Last submission = <string></code>","text":"<p>This option determines what gets displayed on the logbook selection page in the Last submission colum. The default string is <code>$entry time by $author</code>. If a logbook does not contain an <code>author</code> attribute, another string can be chosen.</p>"},{"location":"config.html#id-display-string","title":"<code>ID display = <string></code>","text":"<p>This option determines the display of the entry ID. In some applications, the entry ID can be used as a tag, containing more than just the ID number. For example</p> <p><code>ID display = TAG-$message id</code></p> <p>would display the entry ID as \"TAG-1\",\"TAG-2\", ... and so on.</p>"},{"location":"config.html#prepend-on-reply-string","title":"<code>Prepend on reply = <string></code>","text":"<p>With this option a string can be placed on top of a reply. Using string substition, this can be useful for adding the author and the date of a reply, like</p> <p><code>Prepend on reply = Added $date by $long_name\\n\\n</code></p> <p>where \"\\n\" causes a line break.</p>"},{"location":"config.html#append-on-reply-string","title":"<code>Append on reply = <string></code>","text":"<p>Same as before, but gets added after the previous entry.</p>"},{"location":"config.html#prepend-on-edit-string","title":"<code>Prepend on edit = <string></code>**","text":""},{"location":"config.html#append-on-edit-string","title":"<code>Append on edit = <string></code>","text":"<p>Same as before, but for editing entries.</p>"},{"location":"config.html#sort-attributes-list","title":"<code>Sort Attributes = <list></code>","text":"<p>For the list display, the entries are normally sorted by their ID. Alternatively, one can specify one or more (separated by commata) attributes, which are used for sorting. The first attribute in the list has the highest priority. Only if two entries have the same value in the first sort attribute, they are sorted according to the second sort attribute and so on. To the list of attributes one can add ID, Date and logbook, although ID makes only sense together with other attributes, since it is sorted as the primary key anyhow.</p>"},{"location":"config.html#conditional-attributes","title":"Conditional attributes","text":"<p>When entering data into a elog form, it might be helpful to change the options of the attributes depending on the value of other attributes. Let's assume you have a logbook containing entries for different computers with different operating systems. Your elogd.cfg file starts like that:</p> <pre><code>Attributes = PC Name, Operating System, Version\nOptions Operating System = Linux, Windows\n</code></pre> <p>For the operating system version, you would like a list, but this list has to be different for Linux and Windows. This can be achieved with conditional attributes. Simply write following configuration:</p> <pre><code>Attributes = PC Name, Operating System, Version\nOptions Operating System = Linux{1}, Windows{2}\n{1} Options Version = 2.2, 2.4, 2.6\n{2} Options Version = ME, 2k, NT, XP\n</code></pre> <p>If you enter a new entry into that logbook, the drop-down list for <code>Version</code> changes automatically depending on the <code>Operating System</code>. Note that you have to enable Java Script for this to work. Without Java Script, a separate button appears in the line of the Operating System which has to be pressed to make the Version list change.</p> <p>The number {1} and {2} in the configuration file are called conditions. Depending on these conditions, certain other lines can be activated. So if the Operating System Linux is selected, condition {1} is true, which selects the line starting with {1} to select the options 2.2, 2.4, 2.6.</p> <p>This technique offers various other possibilities, since any configuration option can be made conditional by adding a <code>{<n>}</code> in front of that line where <n> is an arbitrary number. One often used possibility is the definition of forms. Depending on an attribute, the configuration option <code>Preset text = ...</code> can be used to copy some pre-defined forms into the message body, which can then be filled out. Consider following example:</p> <pre><code>Attributes = Author, Type\nOptions Type = Network check{1}, System check{2}\n\n{1} Preset text = network.txt\n{2} Preset text = system.txt\n</code></pre> <p>This causes two text files network.txt and system.txt to be copied into the message body when a new entry is made. The file network.txt could look like:</p> <pre><code>Routers checked: [ ]\nDHCP checked: [ ]\nComment: ...\n</code></pre> <p>This works like a pre-defined form, the user puts X's between the \"[]\" when that item has been checked. Other possibilities are pre-defined shift sheets in environments where elog is uses as a shift logbook. The shift sheet could contain the names of the shift crew, some check-list for standard tasks etc.</p> <p>Another use of conditional attributes is in conjunction with the option <code>Message comment</code>. Depending on some attribute values, different message comments can be displayed to tell the user what to enter exactly in the message body for that attribute value.</p>"},{"location":"config.html#show-attributes-edit-list_1","title":"<code>Show Attributes Edit = <list></code>","text":"<p>When using conditional attributes, it might be necessary to omit certain attributes under certain conditions, to make the input mask shorter and maybe change the order of the attributes. With this option, a subset of all attributes can be specified which get displayed on the single entry page in the same order as they are specified here. This option mainly makes sense when used with conditions, such as:</p> <pre><code>Attributes = PC Name, Operating System, Version, Distribution\nOptions Operating System = Linux{1}, Windows{2}\n{1} Show Attributes Edit = Operating System, Distribution, PC Name\n{2} Show Attributes Edit = Operating System, PC Name, Version\n</code></pre> <p>The above statements cause the atrribute <code>Version</code> to be only visible when \"Windows\" is selected, and <code>Distribution</code> to be only visible when \"Linux\" is selected. If \"Windows\" is selected, the PC name is shown before the version.</p>"},{"location":"config.html#multiple-conditions","title":"Multiple conditions","text":"<p>It is possible to define conditions in more than one options list. The only requiremnt is that conditions are uniquie, meaning that a condition in one option list cannot be used in another list. This can easily be avoided by using numbers for one condition and letters for the other condition, like in the following example:</p> <pre><code>Attributes = PC Name, Operating System, Version, Location, Floor\nOptions Operating System = Linux{1}, Windows{2}\nOptions Location = Main Building{a}, New Building{b}, Old Building{c}\n{1} Options Version = 2.2, 2.4, 2.6\n{2} Options Version = ME, 2k, NT, XP\n{a} Options Floor = Ground, First, Second\n{b,c} Options Floor = Ground, First\n</code></pre> <p>It is possible to specify an OR of several conditions like in the case {b,c}. This is also possible over several conditions, like {1,a} would mean \"The PC has Linux or is in the Main Building\". To specify a AND between conditions, a \"&\" is used. The condition</p> <p><code>{1&a} ...</code></p> <p>specifies for example the condition \"Linux AND Main Building\". If several lines with condition combinations are true, the upper one is used.</p>"},{"location":"config.html#conditions-in-the-list-display","title":"Conditions in the list display","text":"<p>Conditional attributes are usually only used for change items in the entry form. It might however be desirable to have conditional attibutes also working in the list display (the page where several entries are shown on a single page). The value of one attribute can then for example change which other attributes gets displayed via the <code>list display</code> option. To enable the evaluation of conditional attributes for the list display, on uses the option</p>"},{"location":"config.html#list-conditions-1","title":"<code>List conditions = 1</code>","text":"<p>It should be noted that this option can cause a significant performance degradation if many conditional attributes are defines, so it should only be turned on when it is really needed.</p>"},{"location":"config.html#access-control","title":"Access control","text":"<p>Note: Starting with version 2.9.0, the password level access using the options Read password, Write password and Admin password is not supported any more. Please use the user level access as described below.</p>"},{"location":"config.html#password-file","title":"Password file","text":"<p>Access control is done on a user level with a password file. When a user logs in, a session ID is created and placed as a \"cookie\" in the browser. Using this cookie, the user can workin on the logbook until the cookie expires. For this it is necessary that cookies are enabled in the browser.</p> <p>Following options can be used to control the behavior:</p>"},{"location":"config.html#password-file-file","title":"<code>Password file = <file></code>","text":""},{"location":"config.html#login-expiration-hours","title":"<code>Login expiration = <hours></code>","text":""},{"location":"config.html#admin-user-user-list","title":"<code>Admin user = <user list></code>","text":""},{"location":"config.html#login-user-user-list","title":"<code>Login user = <user list></code>","text":"<p>This file contains user names and passwords in XML format, such as</p> <pre><code><?xml version=\"1.0\" encoding=\"ISO-8859-1\"?>\n<!-- created by MXML on Tue Nov 07 08:15:51 2006 -->\n<list>\n <user>\n <name>stefan</name>\n <password encoding=\"SHA256\">Ebx/a.9tFFQ/iUW3mU8GbnPpCVk74jFt56CmiJXVwdm</password>\n <full_name>Stefan Ritt</full_name>\n <last_logout>Tue Oct 17 12:59:47 2006</last_logout>\n <last_activity>Tue Nov 07 08:15:51 2006</last_activity>\n <email>stefan.ritt@psi.ch</email>\n <email_notify>\n <logbook>demo</logbook>\n </email_notify>\n </user>\n <user>\n <name>midas</name>\n <password encoding=\"SHA256\">t56CmiJXVwdmEbx/a.9tFFQ/iUW3mU8GbnPpCVk74jF</password>\n <full_name>Midas User</full_name>\n <last_logout>0</last_logout>\n <last_activity>0</last_activity>\n <email>midas@psi.ch</email>\n <email_notify>\n <logbook>demo</logbook>\n </email_notify>\n </user>\n</list>\n</code></pre> <p>The passwords are encoded. New users can either be created by hitting Register as new user on the login page if <code>Self register = 1</code> in the configuration file, or by the admin user in the Config page by pressing New user. The password file resides in the same directory as the logbooks. When a user is logged it, the entry for this user can be modified via the Config command.</p> <p>To start a new password file, follow these steps:</p> <ul> <li>Specify a password file name with <code>Password file = <file></code> in the configuration file</li> <li>Connect to the logbook. You will be presented with the new user page. Enter the user login name, full name, email and password, then click on the \"Save\" button.</li> <li>Add <code>Admin user = <user></code> into the configuration file, using your login name from above</li> <li>If you now enter the \"Config\" page, you can add other users</li> <li>Remove the self registration option if you like</li> </ul> <p>The presence of a password file requires all users to \"log in\" using their name and password, except when a guest login is allowed via the \"Guest menu commands\" option. An additional advantage of this method is that the user name can be used as an attribute value for creating logbook entries. For example, the following line could be added to the configuration file to fill in the Author and the Email attributes with the current user name and email:</p> <p><code>Attributes = Author, Email, ...</code> <code>Subst Author = $long_name from $remote_host</code> <code>Subst Email = $user_email</code></p> <p>Thus the author name is not user-input anymore, ensuring the entry always contains the actual user name. For a full listing of substitutions, see the \"Subst <attrib>\" option.</p> <p>The user name and password are stored as cookies on the user side. The expiration is controlled by the <code>Remember me</code> checkbox during the login. If unchecked, the cookies expire after the current browser session. If checked, they expire after 31 days by default, which can be changed with the <code>Login expiration</code> option, giving the expiration time in hours. Setting this to 24 for example, makes the password expire after one day. If presistent cookies are not desired, the <code>Login expiration</code> option can be set to zero, in which case the <code>Remember me</code> checkbox is not displayed.</p> <p>The <code>Admin user = <user list></code> is a list of one or more user names, which have admin rights. They see a button <code>Change elogd.cfg</code> on the config page by which they can edit elogd.cfg through the web. They can also modify other users on the <code>Config</code> page, change their passwords or remove them. In addition, the admin user(s) can delete or edit entries from other users if <code>Restrict edit = 1</code>.</p> <p>The <code>Login user = <user list></code> is a list of users who can log in to a specific logbook. This option can be used with a global password file. If a <code>Password file</code> is present under the <code>[global]</code> section, the registered users in that password file can log in to all logbooks. It might be required that only certain users can log in to certain logbooks. This can be achieved with the <code>Login user</code> option, places in each individual logbook section in the configuration file. Only those users listed in this statement can log in to the logbook where the statement is defined. This method has the advantage over the option of definining individual password files for individual logbooks that only one central password file exists. So if a user changes her/his password, this becomes then valid for all logbooks. If there would be individual logbook password files, one would have to change the password in all logbooks individually.</p>"},{"location":"config.html#self-register-01234","title":"<code>Self register = 0|1|2|3|4</code>","text":"<p>With this option it is possible for new users to self-register an user account. At the login page, a link is displayed \"Register as a new user\" which leads the user to a configuration page where one can enter the account name, full name and email address. A flag allows for automatic email notification on new entries on the logbook. These settings can later be changed with the Config menu command.</p> <p>Setting this option to 0 disables self registration. With option 1, users can silently register, while setting it to 2 causes elogd to send an email notification to the admin user(s). The option 3 is used to only send an email notification to the admin users(s), which then can validate the account and commit it by hitting the URL given in the email notification. Setting this to 4 causes and email notification to be sent to the user, which then can validate the account herself/himself proving to have a working email account.</p>"},{"location":"config.html#allow-password-change-01","title":"<code>Allow password change = 0|1</code>","text":"<p>Enables or disabled the ability for users to change their password. If disabled, the \"Forgot password? link in the login page is ommitted as well. The admin user(s) can always change passwords.</p>"},{"location":"config.html#allow-command-user-list","title":"<code>Allow <command> = <user list></code>","text":"<p>Commands can be restricted to certain login names (separated by commas). For each command in the list defined with the \"Menu commands\" option, a list of user names can be specified, which are allowed to execute that command. If the allow option is not present, all users may execute that command by default.</p>"},{"location":"config.html#deny-command-user-list","title":"<code>Deny <command> = <user list></code>","text":"<p>Used to deny a certain command to a list of users. This can be used to deny a guest user to enter new messages or modify a message.</p>"},{"location":"config.html#hosts-allow-list","title":"<code>Hosts allow = <list></code>","text":""},{"location":"config.html#hosts-deny-list","title":"<code>Hosts deny = <list></code>","text":"<p>These two settings can be used to restrict the access to the logbook to certain computers. It is similar to the UNIX hosts.allow and hosts.deny files. The list can consist of individual host names or IP numbers, subnet masks like <code>123.213.</code> (note the trailing '.') or <code>.mit.edu</code>, or the word <code>All</code>. The following rules are applied:</p> <ul> <li>Access will be granted when a host matches a pattern in \"hosts allow\".</li> <li>Otherwise, access will be denied when a host matches a pattern in \"hosts deny\".</li> <li>Otherwise, access will be granted.</li> </ul> <p>These rules are applied before any password is checked. To debug problems, start <code>elogd</code> with the \"-v\" flag, in which case the rule checking is printed on the screen.</p> <p>The global option <code>Logfile = <filename></code> can be specified to log all user login/logout activities plus all successful user connections.</p> <p>If any of the password statements are in the <code>[global]</code> area of the configuration files, they are used for all logbooks. If one logs in at one logbook, access is automaticlly granted to all logbooks. If the password statements are in the individual logbook sections, one has to log in to each logbook separately.</p>"},{"location":"config.html#kerberos-authentication","title":"Kerberos authentication","text":"<p>Starting from version 2.9.0, site authentication has been implemented in elog using the Kerberos authentication scheme. This widely used system is also used in MS Windows Domain Controllers, and can be used for site logins, meaning that the same credentials can be used on all computers of a site.</p> <p>To use that authetication, Kerberos has to be installed on the server running the elogd daemon. Please read the Kerberos documentation how to do this or talk to your site administrator. There are packages for Linux, Windows and Mac OSX. If you compile the elogd program yourself, make sure to have the flag **<code>HAVE_KRB5</code>> defined in the compilation process. To configure elogd to use Kerberos, use following options:</p>"},{"location":"config.html#authentication-methods","title":"<code>Authentication = <method(s)></code>","text":""},{"location":"config.html#kerberos-realm-realm","title":"<code>Kerberos Realm = <realm></code>","text":"<p>where <method(s)> can be <code>File</code> or <code>Kerberos</code> or both such as in <code>Kerberos, File</code>. If the authentication option contains Kerberos, the user credentials are authenticated using the default Kerberos Realm. This is typically obtained from the file <code>c:\\windows\\krb5.ini</code> (Windows) or <code>/etc/krb5.conf</code> (Linux). If another than the default realm should be used, this can be overwritten with the <code>Kerberos Realm</code> option.</p> <p>When Kerberos authentication is used, the password file is still used to store additional user information such as the full name and the email address, but the authentication is done via the Kerberos server.</p> <p>If both authentications <code>Kerberos, File</code> are enabled, the credentials are first authenticated via the Kerberos server, and - if not successful - via the password file. This allows combined elog installations with centralized and local elog accounts. If the Kerberos authentication was successful, the password in the password file is overwritten with the encrypted Kerberos password. This allows the system to work even if the Kerberos server is temporarily not accessible.</p> <p>If the password is changed via the \"Change Password\" button on the config page, the system tries to change the password in the Kerberos database. On some installation it has been found that this does not work, in which case you have to change your password by other means (such as via the Windows login if you use a Windows Domain).</p> <p>Beside the Kerberos authentication, elogd version 3.0 and higher can be configured to accept a authentication done by the webserver.</p>"},{"location":"config.html#authentication-webserver","title":"<code>Authentication = Webserver</code>","text":"<p>You can also combine it with other authentication methods as shown for Kerberos.</p> <p>Elogd is then accepting the username set in the Request-Header \"X-Forwarded-User\" as already logged in.\\ To make this work, you need to configure the webserver correctly, as describe in the adminguide.</p>"},{"location":"config.html#ldap-authentication","title":"LDAP authentication","text":"<p>LDAP (lightweight Directory Access Protocol) has been implemented by vykozlov in a separate branch at https://github.com/vykozlov/elog-ldap. The code has been merged into this distribution on an as-is basis. Following info has copied from the link above:</p> <p>To use LDAP authentication, do the following:</p> <ul> <li>Enable LDAP authentication in the <code>Makefile</code> by setting <code>USE_LDAP = 1</code></li> <li>Change elogd.cf to contain LDAP authentication:</li> <li><code>Authentication = LDAP</code></li> <li><code>LDAP server = ldap://example.org:389</code></li> <li><code>LDAP userbase = ou=People;dc=example,dc=org</code></li> <li><code>LDAP login attribute = uid</code></li> <li><code>LDAP register = 1</code></li> </ul> <p>The <code>login attribute</code> is from the DN (distinguished name), e.g. uid=user,ou=People,dc=example,dc=org. The <code>register</code> flag determines if LDAP users are automatically stored in the local password file, which is necessary for email notifications.</p> <p>Please note that it is not possible to change a password in the LDAP database from within ELOG.</p>"},{"location":"config.html#pam-authentication","title":"PAM authentication","text":"<p>PAM (Pluggable authentication modules) support has been implemented by Jan Christoph Terasa. To use PAM in elogd, do the following:</p> <ul> <li>Compile <code>elogd</code> with PAM support, by either setting <code>USE_PAM = 1</code> in the <code>Makefile</code>, or by specifying it when invoking <code>make</code>. If you compile via CMake, set USE_PAM via ccmake.</li> <li>Enable PAM authentication in <code>elogd.cfg</code>:</li> <li><code>Authentication = PAM</code></li> <li><code>Password file = elogd.passwd</code></li> <li><code>Self register = 3</code></li> </ul> <p>The <code>Password file</code> is used to store the user names and email addresses of PAM authenticated users, since this information can not be (universally) requested via PAM. For security reasons the password file does not store a hash of the user password. Self registration has to be enabled (<code>Self register \u2265 1</code>) to use PAM authentication. - To be able to use PAM, the PAM module in <code>elogd</code> needs to be able to access the authentication facilities on the system (e.g. be able to read <code>/etc/shadow</code>). This can be achieved by either running <code>elogd</code> as <code>root</code>, or by specifying the appropriate SUID/GUID values for the binary. [WARNING:]{style=\"color:red\"} When running elogd as root, be careful when using the <code>-x</code> option to enable execution of commands via <code>$shell</code>, since the commands will be executed using the access rights of the user running <code>elogd</code>!</p> <p>Please note that it is not possible to change the PAM password within ELOG. Instead, please use the available methods on the system</p>"},{"location":"config.html#email-notification","title":"EMail notification","text":"<ul> <li><code>Email <attribute> <value> = <list></code></li> <li><code>Use Email Subject = <string></code></li> <li><code>Use Email Subject Edit = <string></code></li> <li><code>Use Email From = <string></code></li> <li><code>Default Email From = <string></code></li> <li><code>Use Email Heading = <string></code></li> <li><code>Use Email Heading Edit = <string></code></li> <li><code>Omit Email To = 0|1</code></li> <li><code>Suppress Email to users = 0|1</code></li> <li><code>Email attributes = <list></code></li> <li><code>Use Email URL = <URL></code></li> </ul> <p>To send email automatically when new entries are created in a logbook, a <code>SMTP host =</code> entry must be present in the <code>[global]</code> section of the configuration file. To submit an email based on an attribute value, use the statement <code>Email <attribute> <value> = <list></code>. Whenever an entry is submitted where <code>attribute</code> is equal to <code>value</code>, an email notification is sent to the email addresses in <code>list</code>. Several mail addresses may be supplied, separated by commas. The mail addresses can contain attributes via the \"\\$\" substitution. If a logbook contains for example an attribute name which contains email names, then one can put \\$name@domain to form a valid email address.</p> <p>Multiple <code>Email xxx</code> statements may occur in a configuration file. If either the attribute or the value contains one or more blanks the string must be enclosed with quotation marks, as in:</p>"},{"location":"config.html#email-type-normal-routine","title":"<code>Email type \"Normal routine\" = ...</code>","text":"<p>The statement <code>Email All = <list></code> sends an email notification independent of the type and category. The <code>Use Email Subject = <string></code> statement specifies which text is used as the email subject. The text can contain <code>$<attribute></code> statements which are substituted with the current value of that attribute. For a full list of possible substitutions, see the \"Subst <attribute>\" option. The <code>Use Email Heading = <string></code> specifies the text for the email heading line. Default is \"A new entry has been submitted on [host]\". The option <code>Use Email Heading Edit = <string></code> works the same way for updated (edited) entries.</p> <p>The option <code>Use Email From = <string></code> is used for the \"From:\" field in the email. Since more and more email servers do not accept invalid \"From:\" addresses in order to reduce spam mail, it might be important that a \"real\" email address is used in the \"From:\" field. If <code>Use Email From</code> is present, it is always used. If not, the email address of the currently logged in user is used for the \"From:\" field. If no user is logged in, or the current user has not specified a email address in the password database, the setting of the option <code>Default Email From</code> is used for the \"From:\" field. Only if this option is not specified, a generic address ELOG@<hostname> is used, which might be rejected by the SMTP server however.</p> <p>If the flag <code>Omit Email To</code> is set to 1, the To: field in the email is left empty instead set to the real email address of the recipients. This can be useful if one recipient should not see the email addresses of the other recipients.</p> <p>The flag <code>Suppress Email to users</code> can be set to \"1\" if email should only be sent to the recipients of the <code>Email <attribute> <value> = <list></code> statements but not to the users who have registerd for automatic email notification.</p> <p>If one wants to send only some attributes but not all in an email notification, one can use the option <code>Email attributes = <list></code>, where a subset of the attributes can be specified as well as their order. []{#flags}</p> <p>The option <code>Use Email URL = <URL></code> can be used to set the URL of the ELOG logbook used in email notifications. This can be useful if no <code>URL = ...</code> statement is used form some reason.</p>"},{"location":"config.html#flags","title":"Flags","text":""},{"location":"config.html#show-text-01","title":"<code>Show text = 0|1</code>","text":"<p>This flag controls if logbook entries contain a body text. If an installation only requires attributes, this flag can be set to 0. Default is 1.</p>"},{"location":"config.html#enable-attachments-01","title":"<code>Enable attachments = 0|1</code>","text":"<p>This flag controls the attachment submission at the bottom of a message entry page. If this flag is 0, the attachment section is not displayed. This might be useful for logbooks where attachments are not used. Default is 1.</p>"},{"location":"config.html#show-attachments-01","title":"<code>Show attachments = 0|1</code>","text":"<p>This flag controls the display of attachments such as images on normal logbook pages. For logbooks with large images, this flag can be turned off, so that attachments are only displayed when they are clicked on. Default is 1.</p>"},{"location":"config.html#preview-attachments-01","title":"<code>Preview attachments = 0|1</code>","text":"<p>This flag controls the display of attachments in the edit form. If one one uploads an attachment, but has not yet submitted the entry, the uploaded attachments are shown at the bottom if this flag is 1. Only ASCII files and images are shown of course. Default is 1.</p>"},{"location":"config.html#summary-lines-x","title":"<code>Summary lines = x</code>","text":"<p>This specifies the number of text lines displayed in a summary page. Zero displays no text at all. The default is 3.</p>"},{"location":"config.html#summary-line-length-x","title":"<code>Summary line length = x</code>","text":"<p>This specifies the number of charactes of the summary lines. After this number of charactes, a line break is inserted in long lines to keep the column width not too wide. The default is 40.</p>"},{"location":"config.html#attachment-lines-x","title":"<code>Attachment lines = x</code>","text":"<p>This specifies the number of text lines displayed for ASCII attachments. For long ASCII attachments, it can be useful to only display the first few lines not to make the HTML page too long. The default is 300.</p>"},{"location":"config.html#reverse-sort-01","title":"<code>Reverse sort = 0|1</code>","text":"<p>If this flag is 1, all listing pages (the default page view, the result of a search query and the result of the \"Last day\" query) is sorted in reverse order (newest entry down to oldest). The checkbox Sort in reverse order on the search form gets checked by default, too. Sorting in reverse order can make sense if there are many pages of entries, but the ones entered last should be displayed on the first page. Default is 0.</p>"},{"location":"config.html#search-all-logbooks-012","title":"<code>Search all logbooks = 0|1|2</code>","text":"<p>If this flag is 1 or 2, the search form displays the button \"Search all logbooks\". If the flag is 2, the button is checked by default. Setting this flag to 0 hides this button. It might be necessary to do this for public logbooks if there are also protected logbooks. Otherwise the search result would also display entries from the protected logbooks. The default is 1.</p>"},{"location":"config.html#enable-browsing-01","title":"<code>Enable browsing = 0|1</code>","text":"<p>If this flag is 1, browsing (hitting the next/previous button) is enabled. For some rare occasions it might be necessary to disable browsing. Default is 1.</p>"},{"location":"config.html#filtered-browsing-01","title":"<code>Filtered browsing = 0|1</code>","text":"<p>If this flag is 1, browsing (hitting the next/previous button) can be filtered by individual attributes. If the checkbox next to an attribute is checked, only messages with the same attribute value are displayed. Default is 0.</p>"},{"location":"config.html#default-encoding-012","title":"<code>Default encoding = 0|1|2</code>","text":"<p>This specifies the default encoding for new entries. For installations where entries are normally submitted as plain text, the default can be set to 1. Set to 0 for ELCode encoding, to 2 for HTML encoding. The default is 2, which activates the built in FCKeditor automatically for new installations. If this editor is not wanted or people are concerned about cross site scripting, the default encoding should be set to 0 or 1.</p>"},{"location":"config.html#allowed-encoding-n","title":"<code>Allowed encoding = <n></code>","text":"<p>Allowed encoding options. <code><n></code> can be the sum of following flags: - 1 : Plain - 2 : ELCode encoding - 4 : HTML encoding</p> <p>To allow plain and HTML encoding for example, set <code><n></code> to 5. Default is 7. Note that allowing HTML encoding may cause some security risk, since an elog entry may contain malicious scripting code. It should therefor only be allowed for installations where it is really needed and with no public write access.</p>"},{"location":"config.html#allow-html-01","title":"<code>Allow HTML = 0|1</code>","text":"<p>This flag allows or denys the usage of HTML in attributes. Note that allowing HTML encoding may cause some security risk, since an elog entry may contain malicious scripting code. It should therefor only be allowed for installations where it is really needed and with no public write access. The default value is 0.</p>"},{"location":"config.html#suppress-default-0123","title":"<code>Suppress default = 0|1|2|3</code>","text":"<p>This specifies the default state of the \"Suppress Email notification\" button on the new message entry form. For installations where normally an email notification is not necessary, the default can be set to 1. If an important entry is entered, users can then uncheck the suppress box. If this value is set to 2 , the suppress box is not displayed at all, so that an email notification is always produced. If this value is set to 3, the email notification is always suppressed. The default is 0.</p>"},{"location":"config.html#suppress-email-on-edit-0123","title":"<code>Suppress Email on edit = 0|1|2|3</code>","text":"<p>This is the same as <code>Suppress default</code>, but just for edited entries. The default is 0.</p>"},{"location":"config.html#resubmit-default-012","title":"<code>Resubmit default = 0|1|2</code>","text":"<p>This specifies the default state of the \"Resubmit as new entry\" button on the edit message entry from. If this button is checked, the current message is removed from its current position in the database and submitted as a new message. This can for example be useful for applications where users want to see which records have been updated recently. If this value is set to 2, the resubmit box is not displayed at all. The default is 0.</p>"},{"location":"config.html#resubmit-replies-01","title":"<code>Resubmit replies = 0|1</code>","text":"<p>If this flag is set to 1 and an entry is resubmited as a new entry and this entry has replies, all replies of this entry are resubmittes as new entries as well. The default is 0.</p>"},{"location":"config.html#display-email-recipients-01","title":"<code>Display Email recipients = 0|1</code>","text":"<p>If this flag is 1, the email recipients are displayed when a logbook entry is entered which produces an email notification. Setting this flag to 0 suppresses this display, in case users need not see that email is being sent and to whom. The default is 1.</p>"},{"location":"config.html#email-format-n","title":"<code>Email Format = <n></code>","text":"<p>Specifies what is sent in an email notification. <n> is the sum of following flags:\\ - 1 : Send heading line \"A new entry has been submitted...\" - 2 : Send attributes - 4 : Send URL of logbook entry - 8 : Send message body - 16: Send optional attachments as email attachments - 32: Send logbook name - 64: Send names of optional attachments</p> <p>So to send for example only the attributes and the URL, set <n> to 6. Default is 63 (send everything).</p>"},{"location":"config.html#email-encoding-n","title":"<code>Email Encoding = <n></code>","text":"<p>Specifies in which encoding an email is sent. <n> is the sum of following flags:\\ - 1 : Plain text - 2 : HTML in the form of the plain text, but with ELCode interpreted - 4 : Full HTML page as shown in elog</p> <p>So to send email in plain text and full HTML, set <n> to 5. Some email clients have the possibility then to switch from one view to the other. Default is 2.</p>"},{"location":"config.html#max-email-attachment-size-n","title":"<code>Max email attachment size = <n></code>","text":"<p>This option specifies the maximum allowed email attachment size for email notifications. Most mail delivery systems have a maximum attachment size and refuse to accept emails with larger sizes. If the size of an attachment exceeds this limit, it is not included in the email notificaiton but rather a link to the attachment on the elog server is used. The default value is 10000000 (ten million bytes).</p>"},{"location":"config.html#back-to-main-01","title":"<code>Back to main = 0|1</code>","text":"<p>If this flag is 1, the \"List\" button takes you back to the logbook selection page instead to the last entry of the current logbook. The default is 0.</p>"},{"location":"config.html#logout-to-main-01","title":"<code>Logout to main = 0|1</code>","text":"<p>If this flag is 1, the \"Logout\" operation takes you back to the logbook selection page instead to the login page. The default is 0.</p>"},{"location":"config.html#logout-to-url-url","title":"<code>Logout to URL = <URL></code>","text":"<p>If this URL is set, the \"Logout\" operation takes you to a specific web page specified in the URL.</p>"},{"location":"config.html#list-after-submit-01","title":"<code>List after submit = 0|1</code>","text":"<p>If this flag is 1, the list page is shown after the submission of a new entry. If this flag is 0, the entry just submitted is shown. The default is 0.</p>"},{"location":"config.html#restrict-edit-01","title":"<code>Restrict edit = 0|1</code>","text":"<p>If this flag is 1, users can only edit their own messages. The system checks automatically if the currently logged in user matches the user supplied in an author attribute via the \"Preset xxxx\" option. The default is 0.</p>"},{"location":"config.html#expand-default-0123","title":"<code>Expand default = 0|1|2|3</code>","text":"<p>This setting determines how messages are displayed in threaded mode. Following options are possible: - 0: Only message heads are displayed, no replies. A \"+\" indicates which message has one or more replies. - 1: Messages and replies are displayed, but no message body. - 2: Messages and replies are displayed together with the first few lines of the message body. The number of lines is controlled by the <code>Summary lines</code> option. - 3: Messages and replies are displayed together with the full message body.</p> <p>The default is 1.</p>"},{"location":"config.html#hidden-01","title":"<code>Hidden = 0|1</code>","text":"<p>If this flag is 1, the logbook is not displayed in the initial logbook selection page and in the logbook tabs. This can be useful for logbooks which are only accessed for backup or archiving and would clutter up the logbook list for the normal user. To access hidden logbooks, one has to enter the logbook URL directly, or from a bookmark list. Default is 0.</p>"},{"location":"config.html#hide-comments-01","title":"<code>Hide Comments = 0|1</code>","text":"<p>If this flag is 1, the logbook \"Comment\" is not displayed in the logbook selection page. Default is 0.</p>"},{"location":"config.html#use-lock-01","title":"<code>Use Lock = 0|1</code>","text":"<p>If this flag is 1, a logbook entry is locked when someone edits it (clicking the Edit command). A locked message gets displayed with a little red sign indicating that the message is currently edited by someone and should not be touched. This can be helpful in installations where several people can edit messages. Without locking, the second submission of an edited message overwrites the first submission without notice. Although the sign gets displayed, the message can still be edited (the lock can be \"stolen\"), but it's the user's response to avoid any conflict.</p> <p>Since elog cannot determine if someone keeps a message very long for editing or if only the browser got closed, the locking can show up even if the message is not kept for editing any more. In that case, the message has to be edited again and submitted, to remove the origial lock.</p> <p>Note that logbooks accessible from the internet usually get scanned by search engines. This can lead to situations where the Edit link of each message is \"followed\" by a bot, resulting in all messages being locked. In those cases locking has to be turned off.</p> <p>Since release 2.5.4, some Javascript code has been added to avoid unwanted locks. If someone edits an entry, but then goes away from that page or closes the browser without submitting the changes, a pop-up window appears asking the user to submit the changed entry. Although this works for most browsers in most cases, it could be that Javascript has been turned off in a browser, in which case the stale locks still might appear.</p> <p>Default for \"Use Lock\" is 0.</p>"},{"location":"config.html#show-top-groups-01","title":"<code>Show top groups = 0|1</code>","text":"<p>When using top groups, the root of the elogd server is not accessible any more, to avoid cases where one group can \"see\" the logbooks of the other groups. If this feature is unwanted, the flag <code>Show top groups</code> can be set to <code>1</code>, in which case a list of available top groups is shown.</p>"},{"location":"config.html#fix-text-01","title":"<code>Fix text = 0|1</code>","text":"<p>With this options the main text body can be fixed, so that it cannot be changed via the <code>Edit</code> button later. This feature can be useful for set-ups where some attributed must be changed later, but the text body should be preserved. The default is 0.</p>"},{"location":"config.html#case-sensitive-search-01","title":"<code>Case sensitive search = 0|1</code>","text":"<p>This switch has two meanings. First, it defines the default state of the <code>Case sensitive</code> check box in the \"Find\" page. Second, it determines if the quick filters are case sensitive or not. The default is 0.</p>"},{"location":"config.html#mode-commands-01","title":"<code>Mode commands = 0|1</code>","text":"<p>If this flag is missing or set to 1, the links \"Full\", \"Summary\" and \"Threaded\" are shown on the top of the listing page. If this flag is set to 0, these commands are hidden. This might be useful in logbooks where only one mode makes sense for example.</p>"},{"location":"config.html#suppress-execute-default-01","title":"<code>Suppress execute default = 0|1</code>","text":"<p>External scripts can be called with the <code>Execute new/edit/delete</code> options. If these options are enabled, a checkbox appears which lets the user suppress execution of the external script. The setting of this flag determines the default state of this checkbox. In logbooks where a script should only be ocasionally executed, it could make sense to set this flag to 1.</p>"},{"location":"config.html#preserve-ids-01","title":"<code>Preserve IDs = 0|1</code>","text":"<p>When a logbook entry is copied or moved to another logbook, it obtains a new entry ID in the destination logbook. This can cause problems if the logbook entries reference each other with their IDs. To keep the same ID in the destination logbook, this setting can be set to 1. If an entry with the same ID in the destination logbook exists already, it gets overwritten. Default for this setting is 0.</p>"},{"location":"config.html#collapse-to-last-01","title":"<code>Collapse to last = 0|1</code>","text":"<p>In threaded view, the list of replies can be collapsed into a single entry. If this flag is 1, then the last entry of each thread is shown, otherwise the first thread is displayed. Default for this setting is 1.</p>"},{"location":"config.html#sort-attribute-options-attribute-01","title":"<code>Sort Attribute Options <attribute> = 0|1</code>","text":"<p>If this option is 1, the options for this attribute are sorted alphanumerically. This can be handy when locating options from long lists in drop-down boxes in quick filters for example. Default for this setting is 0.</p>"},{"location":"config.html#allow-branching-01","title":"<code>Allow branching = 0|1</code>","text":"<p>With this option one can probihit \"branching\", which is that an entry gets more than one reply. When branching is prohibited, only linear threads are possible, which is one head entry, one reply to it, then one reply to the reply and so on. Default for this setting is 1.</p>"},{"location":"config.html#enable-smileys-01","title":"<code>Enable Smileys = 0|1</code>","text":"<p>When encoding an entry with ELCode, certain sequenes such as :-) get automatically converted into small \"smiley\" images. If this behavior is not wanted, it can be turned off with this option. The default for this setting is 1.</p>"},{"location":"config.html#refresh-seconds","title":"<code>Refresh = <seconds></code>","text":"<p>The elog listing page can be refreshed periodically with this option. If it is given, the page automatically reloads after <seconds>. This can be useful for logbooks where other people often post entries or where some entries are posted automatically (via the elog utility) and one wants to keep an eye on what's new. The default for this setting is 0 meaning no refresh.</p>"},{"location":"config.html#show-last-default-days","title":"<code>Show last default = <days></code>","text":"<p>In large logbooks, search operations can take quite long, blocking other users from accessing ELOG. On the Find page, one can restrict the search operation to a certain time period, like last day, last week, etc, which makes searching much faster, but restricts it to a certain time in the past. If one forgets however to enter anyting in the Show last drop-down box, then the search again can take quite long. This option pre-selects an option in the Show last drop-down box, so that the user does not have to think about selecting a certain time period. Following options are possible: 0, 1, 3, 7, 31, 92, 182, 364. \"0\" means an unrestricted search default.</p>"},{"location":"config.html#save-drafts-01","title":"<code>Save drafts = 0|1</code>","text":"<p>Starting with version 3.1, ELOG supports auto saving. When text for a new entry is entered in the browser, it might get lost if the browser windows is closed before the entry has been submitted. In order to avoid this, entries can be saved as drafts, to be finished and submitted later. This can be achieved by clicking on the <code>Save</code> button or by the autosave feature (see next option). The <code>Save drafts</code> option turns this feature on or off. Default is <code>1</code>.</p>"},{"location":"config.html#autosave-seconds","title":"<code>Autosave = <seconds></code>","text":"<p>Drafts can be sent to the server regularly after some editing (see previous option). This option determines the interval this is done. The default is <code>10</code> seconds after the last edit. Setting Autosave to zero disables the autosave functionality.</p>"},{"location":"config.html#list-drafts-01","title":"<code>List drafts = 0|1</code>","text":"<p>By default, draft entries are shown in the list display in another browser when the entries are currently edited. This can be confusing to other users since the draft entries are frequently updated. To avoid this, this flag can be se to <code>0</code>, which hides all draft entries in the list view. If they are hidden, the only way to come back to them is to hit the <code>New</code> menu item, in which case the system presents to the user a list of open draft messages to be continued.</p>"},{"location":"config.html#hard-wrap-01","title":"<code>Hard wrap = 0|1</code>","text":"<p>If entries are entered in plain text mode, the browser adds automatically a CRLF at the end of each line where the text wraps. This ensures that the submitted entry has the same line breaks as in the edit box. If this behaviour is not wanted, the adding of hard wraps can be turned off by setting this value to 0. If the user then enters a very long line without hitting the newline key, the long line is preserved which can make it hard to read.</p>"},{"location":"config.html#themes","title":"Themes","text":"<p>Themes are layout and color schemes which determine the look and feel of a logbook (sometimes called \"skins\"). A theme consists of a set of images, which are used for the title banner and browse buttons, and a Cascading Style Scheet (CSS), which defines the colors, fonts and spacing of the ELOG pages.</p> <p>Each theme resides in a separate subdirectory and is specified with the <code>theme = <dir></code> option in the configuration file. Each theme can contain several CSSs, which can be selected with the <code>CSS = <filename></code> option.</p> <p>A default theme is contained in the distribution. If new themes are developed by users, they can be sent back to the author, to be included in future releases.</p> <p>To change colors and fonts, the source of a ELOG page can be examined. All elements use CSS classes which are specified in the <code>class=\"<name>\"</code> statements. These classes can be found in the <code>.../themes/default/default.css</code> file and changed accordingly. For a description of all options, please consult for example the W3C consortium.</p> <p>If the CSS file is edited, most browsers require a \"reload\" to refresh the modified file. The elogd daemon does not have to be restarted after a change in the CSS file.</p> <p>These two images display the same logbook entry using different themes:</p> <p></p>"},{"location":"config.html#mirroring","title":"Mirroring","text":"<p>Sometimes it can be useful to have the same ELOG logbook on two different computers. This might be the case if you travel with your laptop, but want to keep the logbooks from your desktop computer on the laptop. The problem is that if you add an entry on your laptop, the logbooks on the laptop and the desktop get out of sync. Merging only the ELOG database files does not help, since two entries could be made at the same day on the laptop and the desktop, which would lead to a conflict in that day's database file.</p> <p>To solve this problem, mirroring was introduced from Version 2.5.0 on. This technology allows to synchronize one ELOG server with a number of other servers on a per-entry basis. No additional software is needed, only two elogd daemons talking to each other. The synchronization can be executed manually or periodically. If entries are changed/added/deleted on both sides, they get merged properly during synchronization. In order to minimize network traffic, each ELOG server calculates a MD5 checksum for each message, which gets exchanged during synchronization. Only when the MD5 checksum differs, entries are transferred.</p> <p>To set-up mirroring, install two elogd servers on two machines (for testing purpose that also works on one machine with two elogd servers running on different ports). This can be done in two ways:</p> <ol> <li> <p>Automatic configuration</p> <p>A complete elog server can be transferred to a secondary server using the <code>clone</code> command. Assume the existing server resides at <code>http://master.your.domain/</code>, and you want to mirror this server to a new location at <code>http://slave.your.domain/</code>. You do that by installing the elog package at the slave machine, and then executing on the slave:</p> <pre><code>`elogd -C http://master.your.domain`\n</code></pre> <p>or</p> <pre><code>`elogd -C https://master.your.domain`\n</code></pre> <p>for a remote server running under the SSL protocol. Note that you have to put \"Allow clone = 1\" temporarily into the elogd.cfg file of your existing server to allow cloning. This opens a password-free access to your existing server, so remove it immediately after you finished cloning.</p> <p>This command tells elogd to retrieve the configuration file, and optionally all logbook entries and password files from the master machine. Note that both servers must be version 2.5.4 or later. In case of trouble, you can turn on verbose messaging:</p> <pre><code>`elogd -v -C http://master.your.domain`\n</code></pre> <p>which could give some hints. If a logbook on the master server uses restricted access, you have to specify the admin user name and password. After everything has been transferred, you can start elogd in the normal way.</p> </li> <li> <p>Manual configuration</p> <p>First, copy the elogd.cfg file from the master to the slave server. Make sure that the files are identical (except the port setting if you run two servers on the same machine). Then, add the following configuration options. They should be put into the [global] section of the cofiguration file:</p> </li> </ol>"},{"location":"config.html#mirror-server-url-list","title":"<code>Mirror server = <URL-list></code>","text":"<p>This statement specifies one or more mirror servers. Each URL must contain the host, port and possible subdirectory of the remote server, as if you would access it through your browser. A typical statement looks like:</p> <p><code>Mirror server = myhost.mydomain.org:8080, http://another.server.org/elog/, https://yet.another.org</code></p> <p>The URL should not contain any logbook name, this gets added automatically. The second example contains a subdirectory, which is typically used if the elogd daemon runs under an Apache proxy. The third example shows a server running under the SSL protocol.</p>"},{"location":"config.html#mirror-config-0-1","title":"<code>Mirror config = 0 | 1</code>","text":"<p>Normally, only the logbook entries are mirrored. One can also mirror the contents of the elogd.cfg configuration file for individual logbooks. This can be turned on by setting this option to <code>1</code>. Default is <code>0</code>. Only the individual logbook section is mirrored, not the [global] section. Settings which are specific to one server, for example the <code>URL =</code> statement, should then be kept in the [global] section, so that they are not mirrored between different servers.</p>"},{"location":"config.html#mirror-cron-minute-hour-day-month-weekday","title":"<code>Mirror cron = Minute Hour Day Month Weekday</code>","text":"<p>This statement turns on periodic mirroring. The format is similar to the UNIX <code>cron</code> command. Each of the five values can either be an asterisk, which means all possible values, a comma-separated list or a range. It can be explained most easily with examples:</p> Mirror cron meaning 0 3 * * * Every night at 3:00 30 7 1,15 * * At 7:30 every 1st and 15th of a month 0 12 10 10 * Once a year at 12:00 on my birthday 0 7-18 * * 1-5 Once every hour from 7:00 to 18:00 from Monday to Friday <p>Valid ranges for each value are:</p> Item. Range Minute 0-59 Hour 0-23 Day 1-31 Month 1-12 Weekday 0-6 with 0=Sunday, 1=Monday, etc. <p>If mirroring is turned on, it is advisable to use the <code>Logfile =</code> option to turn on logging, so that one can inspect the logfile to see if the mirroring works correctly.</p>"},{"location":"config.html#mirror-user-name","title":"<code>Mirror user = <name></code>","text":"<p>If periodic mirroring is used via the <code>Mirror cron =</code> statement and the remote logbook uses user-level access, this statement specifies the user name which is used to log in to the remote logbook. The password is taken from the local password file and has to match the password in the remote password file, otherwise the access is not allowed. The user name is typical the login name of the administrator.</p>"},{"location":"config.html#mirror-simulate-0-1","title":"<code>Mirror simulate = 0 | 1</code>","text":"<p>If one wants to try out mirroring without causing any harm, one can turn on this flag. During synchronization, entries are compared and necessary transfers are displayed, but not executed. Default is <code>0</code>.</p>"},{"location":"config.html#mirror-exclude-0-1","title":"<code>Mirror exclude = 0 | 1</code>","text":"<p>By default, all logbooks are mirrored. Individual logbooks might be excluded from mirroring by putting <code>Mirror exclude = 1</code> in their individual logbook section of the configuration file (Not the [global] section). Default is <code>0</code>.</p> <p>If the statement <code>Mirror server</code> is present in the configuration file, a new menu option <code>\"Synchronize\"</code> appears on the elog page. Clicking on this menu options starts the synchronization:</p> <p></p> <p>On the left side one sees the entry ID's. Entries which are equal locally and remotely are not displayed. Here are the rules for synchronization:</p> <ul> <li>If an entry has been modified locally but not remotely, it is submitted to the remote server.</li> <li>If an entry has been modified remotely but not locally, it is retrieved from the remote server and saved locally.</li> <li>If an entry has been modified remotely and locally since the last synchronization, an error is shown that the entries are conflicting. In that case one has to merge the entries manually and delete it on one side.</li> <li>If an entry has been deleted locally, it is deleted remotely.</li> <li>If an entry has been deleted remotely, it is deleted locally.</li> <li>If a new entry exists locally, it is submitted.</li> <li>If a new entry exists remotely, it is retrieved from the remote server and saved locally.</li> <li>If new entries exist locally and remotely having the same entry ID, the local entries are changed to have higher entry IDs, then the remote ones are retrieved. Care should be taken if external links (such as <code>elog:123</code>) to the local entries are used, since they will point afterwards to the wrong entry.</li> </ul> <p>By starting the synchronization on one elogd server, this server becomes the client and the other one becomes the server. This means that the local server actively compares the local and the remote messages, and updates one or the other if necessary. The other (remote) server does not need to have any mirror option in its configuration file, since the local server simulates a web browser to send and retrieve messages to the remote server. It is however allowed that the remote server also contains some mirror settings in the configuration file, this way the synchronization can be started from both servers.</p>"},{"location":"contrib.html","title":"ELOG Contributions","text":"<p>ELOG contributions can now be found in a separate logbook</p>"},{"location":"demo.html","title":"Demo","text":"<p>A dedicated Demo Logbook is available as a playground.</p>"},{"location":"download_info.html","title":"ELOG download information","text":"<p>ELOG is distributed both as source code and as precompiled binaries for various platforms. In addition to major versions, minor releases are made containing bug fixes or some new and not yet completely debugged code. This is usually the case if some user asks for some new features, which are then implemented and sent to the user for testing. The minor releases are named <code>x.y.z-r</code> where <code>r</code> is the release number. A web access to the source code contains the complete development history of ELOG, plus the newest fixes and features which might yet be in a release. To check out the GIT repository, use:</p> <p><code>git clone https://bitbucket.org/ritt/elog --recursive</code></p> <p>No tags are used, so it is recommended to always use the newest release from the \"master\" branch.</p> <p>Building elogd requires the CMake system and is done in the traditional way:</p> <pre><code>$ cd elog\n$ mkdir build\n$ cd build\n$ cmake ..\n$ make\n</code></pre> <p>This will put the executables <code>elogd</code> and <code>elog</code> into the build directory, from where they can be moved to a system directory like <code>/usr/local/sbin/elogd</code></p> <p>News for each version can be seen in the changelog</p>"},{"location":"download_info.html#binary-packages","title":"Binary packages","text":"<p>Various binary packages are kept in a separate download repository.</p>"},{"location":"download_info.html#windows-binaries","title":"Windows Binaries","text":"<p>The windows binaries are distributed with an automatic installer. Execute the installer to install ELOG and to register the elogd server as a windows service. Previous windows versions can be found here.</p> <p>Note that the windows binaries are very much outdated and will be updated once the develop gets access again to a Windows PC.</p>"},{"location":"faq.html","title":"ELOG FAQ","text":"<p>Frequently Asked Questions about usage and configuration</p> <p>Please check also the ELOG Forum.</p>"},{"location":"faq.html#how-does-one-configure-elog-to-display-the-last-message-by-default","title":"How does one configure elog to display the last message by default","text":"<p>One can use the <code>Start page</code> option for that. The entry:</p> <p><code>Start page = 0?cmd=last</code></p> <p>shows the last message entry by default. To have the described behaviour for all logbooks, the above statements can be placed in the <code>[global]</code> section.</p>"},{"location":"faq.html#are-there-any-plans-to-implement-a-mysql-back-end","title":"Are there any plans to implement a MySQL back end?","text":"<p>No. The idea behind ELOG is that it is a simple to use, simple to install application. Many people use ELOG under Windows, and they even don't know what MySQL means. Other people like the flat file database format, because it's simple, easily accessible from other programs, and it's easy to backup certain days or months of the database (since the filenames contain the date). Since ELOG should be independent of any other package, some \"switchable\" backend between native ELOG format and MySQL would be needed, which is lots of work and not planned right now.</p> <p>However, there are several contributions from other people who wrote scripts to put ELOG entries into a MySQL database. One is available at http://elog.psi.ch/elogs/Forum/387.</p>"},{"location":"faq.html#can-i-run-the-elog-daemon-from-inside-apache-or-any-other-web-server","title":"Can I run the ELOG daemon from inside Apache or any other Web server?","text":"<p>No. The ELOG daemon was designed as a standalone server and it will stay like that in the future. The reason for that is that <code>elogd</code> should not rely on any other software. This is for example important for many people running <code>elogd</code> under Windows, and they have no clue how to install Apache for Windows. The installation and maintenance for <code>elogd</code> therefore becomes much simpler. To run <code>elogd</code> in parallel to an Apache server on port 80, use Apache as a proxy, following the instruction on the installation page (\"Running elogd under Apache\").</p>"},{"location":"faq.html#i-can-access-my-logbook-without-any-password-isnt-that-a-security-problem","title":"I can access my logbook without any password, isn't that a security problem?","text":"<p>By default, no password is used in ELOG. This can be useful for public directories etc. that anybody should be able to read. To add password security, read the documentation under Access control. The recommended setup is password file security with guest access.</p> <p>Note that passwords are transferred over the network in plain text and therefore not secure. If this is a problem, a secure network connection should be used.</p>"},{"location":"faq.html#i-want-a-bookmark-pointing-to-the-last-page-where-an-attribute-has-a-certain-value","title":"I want a bookmark pointing to the last page where an attribute has a certain value","text":"<p>Use the URL:</p> <p><code>http://<your.host>/<logbook>/?cmd=Last&<attribute>=<value></code></p> <p>This executes the \"Last\" command using a filter with <code><attribute>=<value></code>. The following command displays the same page, but also locks the attribute (checks the box next to <code><attribute></code>) so that browsing (next, previous, first, last) only shows pages with that attribute value.</p> <p><code>http://<your.host>/<logbook>/?cmd=Last&<attribute>=<value>&l<attribute>=1</code></p> <p>Note the <code>\"l\"</code> before the second attribute, as in <code>\"*lAuthor=1*\"</code>.</p>"},{"location":"faq.html#i-want-a-logbook-with-public-read-access-no-password-but-restricted-write-access","title":"I want a logbook with public read access (no password), but restricted write access","text":"<p>In an old version of the FAQ it has been stated here that one has to use two logbooks pointing to the same data directory. From Version 2.0.6 on, this can be accomplished much easier by the usage of the \"Guest menu command\". Use a logbook with user level access (password file), and add menu lists like in the following example to the configuration file:</p> <pre><code>Menu commands = New, Edit, Reply, Find, Last 10, Change password, Logout, Help\nGuest menu commands = Find, Last 10, Login, Help\n</code></pre> <p>If users access the logbook without supplying a user name, they are treated like \"guests\" and see the \"Guest menu commands\", with which one cannot submit or edit logbook entries. If one hits the \"login\" button, a user can login with a user name/password and sees the normal menu commands, with which one can submit new logbook entries.</p> <p>An optional self registration is possible by specifying</p> <p><code>Self register = 1</code></p> <p>in the configuration file. New users can then create their own accounts.</p>"},{"location":"faq.html#i-have-many-loogbooks-with-password-files-so-if-i-add-a-user-or-want-to-change-a-password-i-have-to-do-this-for-all-logbooks-which-is-painful","title":"I have many loogbooks with password files, so if I add a user or want to change a password I have to do this for all logbooks which is painful.","text":"<p>You can have several logbooks point to the same password file. So if you change a user or password in that file, it becomes automatically available in all logbooks which use that file.</p>"},{"location":"faq.html#how-can-i-configure-elog-such-that-it-displays-something-else-than-the-message-list-by-default","title":"How can I configure ELOG such that it displays something else than the message list by default?","text":"<p>There is a simple trick. You use the \"Start page\" option in the <code>elogd</code> file to redirect the start page to something else. Here are some examples:</p> <pre><code>?npp=5 for the last 5 messages\n?last=7 show last 7 days (week)\n?cmd=New show the new message entry form\n?cmd=Find Show the \"find\" page\n?cmd=Search&<attrib>=<value> for a search with <attrib>=<value>\n</code></pre> <p>The various URLs can be copied from the browser's address bar when doint various things there.</p>"},{"location":"faq.html#i-want-to-have-additional-commands-specific-to-my-lookbook","title":"I want to have additional commands specific to my lookbook","text":"<p>New commands can be added for example with the <code>\"Bottom text = bottom.html\"</code> option. To display all messages from last week and month of with \"category = info\", one can put following HTML code in bottom.html:</p> <pre><code><center>\n<a href=\"?last=7&Category=Info\">Info from last week</a> |\n<a href=\"?last=31&Category=Info\">Info from last month</a> |\n</center>\n</code></pre> <p>Note that the parameters <code>\"last=7&Category=Info\"</code> applies a filter on the display. You can learn how to make these filters by looking at the URL in your browser when you submit a find command with certain options.</p>"},{"location":"faq.html#how-does-one-configure-elog-to-disable-editing-of-existing-messages-i-want-a-logbook-where-one-can-enter-messages-but-not-change-them-afterwards","title":"How does one configure elog to disable editing of existing messages? I want a logbook where one can enter messages but not change them afterwards.","text":"<p>This works with the option <code>Menu commands</code>. By default, the menu commands <code>Back, New, Edit, Delete, Reply, Find, Config, Help</code> are dispalyed and allowed. To avoid editing (and deleting) of existing messages, one removes the two commands and puts following statement into <code>elogd.cfg</code>:</p> <p><code>Menu commands = Back, New, Reply, Find, Config, Help</code></p> <p>This prohibits the execution of the commands \"Edit\" and \"Delete\".</p>"},{"location":"faq.html#how-can-i-track-various-revisions-of-a-message-using-the-edit-command","title":"How can I track various revisions of a message using the \"edit\" command?","text":"<p>There are two ways:</p> <ul> <li>Add an attribute which keeps the revision dates and names as follows:</li> </ul> <pre><code>Attributes = Author, ..., Revisions\nLocked attributes = Revisions\nSubst on Edit Revisions = $Revisions<br>$date by $long_name\n</code></pre> <p>The \"Revisions\" attribute cannot be modified manually (since it's locked). On each edit, the date and the current author is appedned to the previous revisions. The \"\\<br>\" puts a line break between the entries.</p> <ul> <li> <p>Create a thread for each entry. In addition of having the date and author of different revisions, the message content is kept. To revise and entry, one hits \"Reply\" instead of \"Edit\" (one can disable the \"Edit\" command for example). If one puts following option into the configuration file:</p> <p><code>Reply string = \"\"</code></p> </li> </ul> <p>then the reply contains the original message without the usual \"> \" at the beginning of each line. One can then edit the message and submit it. In the threaded message list display, one sees then the different revisions as a message thread.</p>"},{"location":"faq.html#how-can-i-enter-a-date-which-is-different-from-current-one","title":"How can I enter a date which is different from current one?","text":"<p>Usually, the current date/time is recorded when you add a new entry. It might be, however, that one wants to enter \"old\" entries, or some entries with a date in the future (like a to-do list with a due date). To do that, on can add a new attribute (let's call it Record date, to be different from the pre-defined Date:</p> <pre><code>Attributes = Author, ..., Record date\nType Record date = date\nPreset Record date = $date\nDate format = %Y %m %d\nList Display = Record date, Author, ...\nStart page = ?rsort=Record date\n</code></pre> <p>The Preset Record date statement sets the record date to the current date, but this can then of course edited during the message entry. The List Display and Start page statements show the record date as the first column in the summary display and also sort by that. Note the Date format showing first year, then month and day. This is necessary since sorting is done only lexically. Please note that the List Display was renamed recently. Prior to version 2.3.10, it was called Display Search.</p>"},{"location":"faq.html#i-cannot-pass-the-login-page-its-always-redisplayed-even-if-i-put-in-the-right-password","title":"I cannot pass the login page, it's always redisplayed even if I put in the right password?","text":"<p>This can happen if you change the login policy, for example move the <code>Password file =</code> entry in the configuration file from a logbook section to the [global] section or back. In that case some old cookies could be stored in your browser, which confuse the system. Please delete your cookies in the browser to resolve this problem. Read your browser documentation on how to do that.</p>"},{"location":"faq.html#how-can-i-change-an-attribute-for-an-entire-thread-we-have-an-attribute-open-problemfixed-which-should-be-changed-for-the-whole-thread-if-that-problem-has-been-fixed","title":"How can I change an attribute for an entire thread? We have an attribute \"open problem/fixed\" which should be changed for the whole thread if that problem has been fixed.","text":"<p>This is a typical request of a bug-tracking set-up. Someone enters a request, opening a new thread. The expert(s) reply to the the request, and after a while, the request gets satisfied or the problem gets fixed. If an attribute like \"status\", having the options \"open\" and \"fixed\" could get changed for the whole thread, on could very easily search for all \"open\" problems.</p> <p>Since this functionality is not implemented, an alternative strategy is recommended: Implement two (or more) logbooks. The first logbook has open issues, the second one has fixed ones. When an entry changes state, it simply has to be copied to the second logbook. This can be done by defining the menu command \"move\" in the config file, like:</p> <p><code>Menu commands = Back, New, Edit, Delete, Reply, Find, Move to, Config, Help</code></p> <p>Note the additional Move to. This solution is even more elegant than having attributes changed in whole threads, since one has two separate logbooks, and can treat the second one more like an archive, make separate back-ups, or deleting some entries after some time, while keeping the open issues untouched.</p>"},{"location":"faq.html#can-i-use-rss-feeds-with-password-protected-logbooks","title":"Can I use RSS feeds with password protected logbooks?","text":"<p>RSS feeds normally only work for logbooks which have at least public read access (via the guest menu commands). There is however a way to allow only restricted read access and still use RSS feeds. This is done by adding an additional read password via the <code>elogd -r <pwd> -l <logbook></code> command. This password (username may be any) can then be used in an RSS reader for restricted access. One reader which has been successfully used with this kind of authentication is RSSReader.</p>"},{"location":"faq.html#how-can-i-make-a-whole-thread-open-or-closed","title":"How can I make a whole thread open or closed?","text":"<p>Sometime people want to mark a whole thread in a way. An example is a to-do list, where they want a special icon on high priority things, and have this icon disappear one the task is finished. This can be easily done with icons. The configuration could look like this:</p> <pre><code>Attributes = Author, Status, Subject\nIOptions Status = icon1.gif, icon2.gif, icon4.gif\nPreset Status = icon4.gif\nPreset on reply status = icon2.gif\nIcon comment icon1.gif = Closed entry\nIcon comment icon4.gif = Open entry\nThread display = $Author $Subject\nThread icon = Status\n</code></pre> <p>New entries get an exclamation mark icon for example (\"Preset status = ...\"). Replies to this entry get a reply icon. Once the thread should be closed, one simple edits the top entry in that thread and changes the icon. The icon1.gif from the distribution is maybe not ideally suited for that, but one could make a green check mark icon for example for that. The \"Thread display\" and \"Thread icon\" make this icon appear at the left side of the threaded display.</p> <p>An alternative approach would be to use two logbooks. The first one receive all new entries (\"open items\"). Once an entry (with its replies) gets closed, it must be moved manually to the second logbook (\"closed items\"). This can be done with the \"Move To\" command (see \"menu commands\" in config file). This way one nicely separates open and closed items in two separate logbooks. One can still search both logbooks at the same time if one checks \"Search all logbooks\" in the find page.</p> <p>Starting from elog version 2.7.7, there now even a third way to do this. With an additional line in the configuration file: Collapse tn last = 1 (in fact the default, but to be explicit), then when the thread is ready to be marked as closed, select the \"closed entry\" icon when writing the last entry. When the entries are viewed in \"threaded\" mode, then the closed entry icon appears on the last entry; and when in \"threaded, collapsed\" mode, then the closed entry icon appears in the one line that represents that whole thread.</p>"},{"location":"faq.html#does-elog-have-a-spell-checker","title":"Does elog have a spell checker?","text":"<p>No, but you can use any spell checker which works with your browser. Examples are IESpell for Internet Explorer and SpellBound for Mozilla-based browsers.</p>"},{"location":"faq.html#why-are-entries-with-large-attachments-submitted-so-slowly","title":"Why are entries with large attachments submitted so slowly?","text":"<p>If email notifications are used, the ELOG program has to pass these attachments to the email server, which might take quite some time. Some email servers even don't allow to forward attachments if they are larger than a few mega bytes. In that one can simply turn off the forwarding of email attachments with</p> <p><code>Email format = 111</code></p> <p>this causes only the attachment names being forwarded, not the attachments themselves.</p>"},{"location":"faq.html#the-elgod-daemon-crashes-from-time-to-time-what-can-i-do","title":"The elgod daemon crashes from time to time, what can I do?","text":"<p>Bugs are constantly fixed inside elogd so a upgrade to the current version is recommended as a first measrue. If that does not help, the key will be the reproducibility of the crash. I only can fix problems if I can reproduce them. Sometimes it's related to strange logbook entries which cause elogd to crash when they are edited. So if there is a way to reproducible trigger the problem, I need the files and confiration related with it. If I can reproduce it in my local installation, I can fix it pretty soon.</p> <p>If that is not possible, an alternative is to run elgod under a debugger, and do a stack trace if the program dies. Under linux, this can be done using the gdb debugger, which might look like this:</p> <pre><code>[~/elog]$ gdb ./elogd\nGNU gdb Red Hat Linux (6.5-25.el5rh)\n...\n\n(gdb) run\nStarting program: /afs/psi.ch/user/r/ritt/elog/elogd\nelogd 2.7.5 built Dec 2 2008, 10:47:09 revision 2147\nImageMagick detected\nIndexing logbooks ... test\n\nProgram received signal SIGSEGV, Segmentation fault.\n0x08054beb in el_index_logbooks () at src/elogd.c:3892\n3892 *p = (char)1;\n(gdb) where\n#0 0x08054beb in el_index_logbooks () at src/elogd.c:3892\n#1 0x080b8774 in server_loop () at src/elogd.c:27565\n#2 0x080bbdd5 in main (argc=1, argv=0xbfee5b54) at src/elogd.c:28923\n(gdb)\n</code></pre> <p>So the basic command is to make a stack trace with \"where\" after a segmentation fault. This tells me where in the code something wrong happened (in this case it was inside the function el_index_logbooks() at line 3892. Please send me this information and I will try then to figure out what was wrong.</p>"},{"location":"faq.html#how-can-i-create-an-elog-entry-automatically-from-a-script","title":"How can I create an ELOG entry automatically from a script?","text":"<p>The User's Guide describes the standalone \"elog\" utility, which can be used from a script or from another program to submit an automatic email entry. This works locally or remotely, with optional attachments. Enter \"elog -h\" for a full list of options. The elog utility is part of the distribution and resides in the same directory as the elogd daemon.</p>"},{"location":"faq.html#i-want-to-notify-different-people-for-different-things-how-do-i-set-up-this","title":"I want to notify different people for different things, how do I set up this?","text":"<p>Assume you want to send an email notification to person A for a problem report, to person B for problem fix and so on. The simplest way is to use the <code>Email <attribute> <value> = <email address></code> syntax. So you could set-up following configuration:</p> <pre><code>Attributes = Author, Type\nOptions Type = Problem Report, Problem Fix\nEmail Type Problem Report = person.a@elog.com\nEmail Type Problem Fix = person.b@elog.com\n</code></pre> <p>If you want to select email addresses directly from a list, you can do the set-up as following: Attributes = Author, Notify MOptions Notify = Person A, Person B Email Notify Person A = person.a@elog.com Email Notify Person B = person.b@elog.com This way you can for each entry select one or more people to be notified from the pre-defined list.</p>"},{"location":"forum.html","title":"Forum","text":"<p>A dedicated discussion forum running elog itself is used for various feedback and questions around elog.</p>"},{"location":"userguide.html","title":"ELOG User's Guide","text":"<p>How to get the most from your ELOG server</p>"},{"location":"userguide.html#a-quick-intro","title":"A Quick Intro","text":"<p>ELOG is part of a family of applications known as weblogs. Their general purpose is :</p> <ol> <li>to make it easy for people to put information online in a chronological fashion, in the form of short, time-stamped text messages (\"entries\") with optional HTML markup for presentation, and optional file attachments (images, archives, etc.)</li> <li>to make it easy for other people to access this information through a Web interface, browse entries, search, download files, and optionally add, update, delete or comment on entries.</li> </ol> <p>ELOG is a remarkable implementation of a weblog in at least two respects :</p> <ul> <li> <p>its simplicity of use : you don\\'t need to be a seasoned server operator and/or an experimented database administrator to run ELOG ; one executable file (under Unix or Windows), a simple configuration text file, and it works. No Web server or relational database required. It is also easy to translate the interface to the appropriate language for your users.</p> </li> <li> <p>its versatility : through its single configuration file, ELOG can be made to display an infinity of variants of the weblog concept. There are options for what to display, how to display it, what commands are available and to whom, access control, etc. Moreover, a single server can host several weblogs, and each weblog can be totally different from the rest.</p> </li> </ul> <p>This is actually a problem when writing a User's Guide, because ELOG servers, and individual weblogs on one server, can vary wildly in appearance and functionality... This guide only attempts to cover the main concepts of importance for ELOG users, describing the default \"out-of-the-box\" setup and how that behaviour may have been modified by the server administrator.</p>"},{"location":"userguide.html#what-words-mean-here","title":"What Words Mean Here","text":"<p>Just to be clear, some definitions of terms that will be used throughout the guide :</p> <ul> <li>ELOG server : the machine on which the ELOG server is run. Its operating system (Windows/Unix/Linux) and status (server/desktop) are not important, and of course it will probably do many other things besides.</li> <li>ELOG administrator : the person who has the authority to modify the ELOG configuration file on the server. May be an actual system administrator, a normal user of a server, or just the owner of a Windows PC.</li> <li>logbook : a weblog made available by the ELOG server. There may be many distinct such logbooks on one server.</li> <li>entry : the individual piece of information in a logbook. Can be as basic as a text message with a time-stamp, or carry much more information : attributes (see below), HTML markup, links, attached files...</li> </ul>"},{"location":"userguide.html#accessing-an-elog-server-and-its-logbooks","title":"Accessing an ELOG server and its logbook(s)","text":"<p>To access a logbook, point your Web browser at the appropriate URL. The default for a local Elog is <code>http://localhost:8080/logbookname</code>. Logbook files are stored in directory <code>logbookname</code> 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.</p> <p>If several logbooks are defined on the server, the entry page may be a list of all logbooks, with their descriptions, number of entries, and links to enter the logbook you want to use.</p> <p>Alternatively, you may be taken directly to a specific logbook. By default you will see a list of entries, but the administrator may have defined a different \"default view\" for the logbook, like the list of the day\\'s entries, or directly display the last entry, etc. (depending on what is most convenient for that logbook\\'s purpose).</p> <p>Each entry in a logbook is identified by an unique ID, which is last part of the URL when that message is displayed. This ID might be used to create a bookmark in a browser pointing directly to a specific entry.</p> <p>There are four ways through which access to a logbook may be controlled: it may be open for all to read ; it may require a common \"read\" password for all users ; it may require each user to have an individual user account (login name) and password ; finally, access may be granted or not depending on the address of the workstation you are using.</p>"},{"location":"userguide.html#viewing-information-in-elog","title":"Viewing information in ELOG","text":"<p>There are two main viewing modes in a logbook :</p> <ul> <li>the \"entry\" view : this is when only one entry is displayed on screen (like the latest entry when you first enter a logbook, or if you click on one in a list). Here are the various parts of the display :</li> <li> <p>if there are several logbooks on the ELOG server you will see a row of \"tabs\" at the top with the names of all the logbooks. These are link that allow to switch quickly between logbooks (this may be disabled).</p> </li> <li> <p>below is a title bar with the name of the current logbook at the left, and the ELOG logo at the right. If you are logged in, there will be a \"<code>Logged in as <username></code>\" reminder in between.</p> </li> <li> <p>next is the \"menu bar\" : on the left is a series of links or buttons for ELOG commands available to you. These are explored in the sections below (Note: different users may see different menus). On the right is a \"VCR-like\" set of buttons for browsing, also explained later (this may be disabled).</p> </li> <li> <p>after these comes the actual entry information. It always starts with the entry time-stamp, and may be followed by up to twenty \"attributes\". These are like fields in a database and have been defined specifically for the current logbook. Each attribute has a checkbox besides it, explained below (this may be disabled).</p> </li> <li> <p>the full-width box below holds the textual content (message) of the entry. This can be plain-text or HTML code. Note that for some special applications (say, a photo album or an event log) the attributes and/or the attached files may be enough information, so this field may not always be present.</p> </li> <li> <p>last and optionally, one or more attached files (that were uploaded to the server when the entry was created) are offered as clickable links for download or viewing, along with the file name and size. If these are images they may be displayed directly on the page.</p> <p>At the bottom of every page is a common \"footer\" for the logbook. By default this is just a link to the ELOG home page in Switzerland, but may be customized locally (typically to provide a navigation bar and links for integration with other Web sites). - the \"search result\" views : these are basically lists of entries, resulting either from a \"Search\" command or from shortcuts such as \"Last X days\" and \"Last X entries\" commands (more on this below). This mode has many options, including : - a \"summary\" view : one entry per row in a table. Some attributes may not be displayed. If the entry text is displayed (or its first few lines), it goes into the rightmost column. Attachments are not displayed.</p> </li> <li> <p>a \"classical weblog\" view : entries appear beneath one another, with attributes on one line and the text (and attachments, if present) below. Images may be displayed or just linked to.</p> </li> <li> <p>entries may appear most recent first, or in reverse.</p> </li> <li> <p>menus on list views are different from the entry view menu. By default they only have two or three commands, but they may have been customized by the administrator to add more.</p> <p>All these lists have a number to the left of each listed entry, that is a link to the corresponding entry view.</p> </li> </ul>"},{"location":"userguide.html#browsing-around-and-finding-things","title":"Browsing around and finding things","text":"<p>There are several interesting ways to peruse the information in a logbook :</p> <ul> <li>weblogs\" are often used for applications where chronology (time) is relevant, so a very common approach is to see \"what happened last\". In ELOG there are two commands for this. They are actually shortcuts for searches, to display the last day\\'s (24 hrs) entries, or the last 10 entries (regardless of age). Note that the menus on the \"search result\" views of these commands are a bit special : they have the same command that created them, but with the search \"interval\" doubled. From the \"last day\" list you can get the \"last 2 days\" list, from that one the \"last 4 days\", etc., and similarly for \"last 10\", \"last 20\", etc., making it easy to quickly go back in time.</li> <li>another useful method, very specific to ELOG, is \"filtered browsing\" - again, shortcuts for specific searches. On the entry view, the \"VCR\" buttons normally let you see the previous, next, first or last entry in the logbook. However, if on the current entry you check one (or more) of the checkboxes in front of the attributes, only entries having the same value for the checked attribute(s) will be displayed by the browse buttons. Thus you can quickly flip through all the entries you submitted yourself, or of a certain type/category, depending on what attributes have been defined.</li> <li>for custom searches there is the query form given by the \"Find\" command. This lets you look for entries between two dates, with particular values for any attribute, or containing specific text. If you fill in several fields, only entries that meet ALL criteria will be selected. Possible options include sort order and summary view for results, printer-friendly formatting, displaying attachments or not, and searching through all logbooks on the ELOG server (if applicable).</li> </ul>"},{"location":"userguide.html#adding-stuff-to-a-logbook","title":"Adding stuff to a logbook","text":"<p>If you have \"write access\" to a logbook (by one of the same four methods as for read access), then you may use the \"New\", \"Edit\", \"Reply\" and \"Delete\" commands.</p> <p>For the quality of the information committed to the logbook, you need understand and use these as well as possible. Here are some of the important features for each commmand :</p> <ul> <li>New :</li> <li>you will not be able to save your entry if all attributes marked with a red star (*) are not filled in.</li> <li>some attributes may be pre-filled from system variables (like your user name). Pre-filled attributes may be still editable or read-only (like the entry creation date).</li> <li>attributes may be text fields (limited to 100 characters), list-boxes (max. 100 values), or check-boxes. There is also a special type of attribute where several values are listed on a line with check-boxes, and you can check as many values as needed.</li> <li>a nice touch : URLs in attributes (http://..., ftp://..., mailto:...) are automatically converted to links.</li> <li>in addition to the above URLs, one can enter a tag elog:\\<id> which references another logbook entry. The tag elog:\\<logbook>/\\<id> references a message in another logbook on the same server. The tag elog:\\<id>/\\<n> references attachment number n in a logbook entry. To reference an attachment in the current message, one uses elog:/\\<n>. An anchor inside an entry can be referenced with elog:\\<id>#\\<anchor>.</li> <li>the Text multi-line field, if present, may be pre-filled with a template if entries need to have a common, consistent format across the logbook (especially for HTML). There may also be a comment inserted before it to explain local rules and conventions, upload rules, etc.</li> <li>check the \"Submit as HTML\" box if the entry contains HTML markup.</li> <li>a logbook may be configured to send a notification e-mail to various recipients each time an entry is submitted. This may be the default behaviour, and you should check \"Suppress notification\"\" if it is not wanted. Or it may be checked by default, and you need to explicitely uncheck it to send the mail. Then again, you may not have a choice... (note that notifiation recipients may or may not be disclosed).</li> <li>if the logbook allows attachments, there will be a number of fields with \"Browse\" buttons at the bottom of the form. Use these to pick one or more files on your local computer, they will be uploaded to the ELOG server as you submit the form. IMPORTANT : there is an upper limit on the size of individual attached files. By default it is about 1 MB but can be changed by the administrator.</li> <li>Edit :</li> <li>normally the Edit form will have all the values of the existing entry in its fields for modification. However, sometimes you may see fields that have been blanked if this makes sense for a particular logbook application (e.g. a \"Last modified by\" field).</li> <li>the \"Submit as new entry\" checkbox only appears on Edit forms. If it is unchecked, the modified entry keeps its original creation time-stamp. If it is checked, the modified entry becomes the latest in the logbook, as if it had just been created. Again, it is possible that this is checked by default, or disabled altogether on some logbooks.</li> <li>managing attachments through this form is easy. If all you want to change is the attributes or text, don\\'t touch the fields at the bottom and the original attachments will be preserved. If you want to add an additional attachment, use an empty field. If you want to update an existing file, use the \"Browse\" button below that file\\'s name to specify the new one. Lastly, if you want to delete an attachment without upoading a new one in its place, you must type the magic word \"<code><delete></code>\" in the field below its name.</li> <li>Reply :</li> <li>this command creates a new entry, but with the current entry\\'s text \"quoted\" (with \\'>\\') in the compose form, much like when replying to e-mail.</li> <li>the new entry has a special \"In reply to\" attribute with a link to the original entry ; the latter also acquires a \"Reply\" attribute with a link to the new entry. Unfortunately these links cannot be trusted in the present ELOG storage system, and the whole scheme gets somewhat confusing when there are several replies.</li> <li>Delete :</li> <li>nothing much to say about this one, except that there is no \"Recycle bin\" or whatever : once you have confirmed the deletion of an entry, it\\'s gone for good, so be careful ! (same holds for the replacement or deletion of an attached file).</li> </ul>"},{"location":"userguide.html#misc-tips-tricks-things-to-be-aware-of","title":"Misc. tips & tricks, things to be aware of...","text":"<ul> <li> <p>you can link directly to a specific entry by its URL, using the message ID (from another entry or an external Web page). It is also possible to link to a search result this way: use the \"Search\" form to compose a query that will result in exactly what you want (either a single entry or a list of entries). Copy the URL for that result page from your browser, and use that as the target for your link.</p> </li> <li> <p>right now you cannot search entries for attachments by their file name.</p> </li> <li> <p>right now attributes that consist of just a checkbox (\"boolean\") can only be searched by \"checked\" state in the \"Search\" form. However, if you start from an entry where that attribute is unchecked, you can use \"filtered browsing\" to flip through all other entries where it is also unchecked.</p> </li> <li> <p>as mentioned above, the \"Reply\" command only provides a basic comment/chat facility - a full-blown discussion board is not ELOG's purpose. If a logbook has a very specific purpose and format (picture gallery, event log, file library etc.) it might be a good idea to disable that command there and move all chat/comments/discussions to a separate, dedicated logbook to avoid \"visual pollution\".</p> </li> <li> <p>it is important to understand that currently the ELOG server application is \"single-process\" and \"non-streaming\". In normal terms this means that :</p> </li> <li> <p>only one request is processed at any one time by the server.</p> </li> <li> <p>uploading or downloading an attachement file is a single request, and causes the entire file to be loaded in server memory while the request is being processed.</p> <p>This is not normally a problem for the sort of short, text-mode entries ELOG is designed to support. However, if a user starts to upload or download a large attachment file (or image) over a slow link, all other users on that ELOG server will have to wait for that transfert to finish before they can access any logbook on that server. This is why there is a low limit on the size of attachments, and why ELOG should not be used to distribute large files under intensive multi-user conditions.</p> </li> <li> <p>It is possible to use bookmarks to pre-populate various attributes when submitting an ELOG entry. This can be useful if the same person often creates similar entries from the same PC. For example, with a bookmark of the form:</p> <p>http://your.host/your_logbook/?cmd=New&pauthor=joe&ptype=Info</p> </li> </ul> <p>...a new entry is created, with the \"author\" field pre-populated with \"joe\" and the \"Info\" value preselected for the \"type\" field. The same is possible for any attribute defined in the logbook (note the leading \"p\"). Thus you can define a set of bookmarks for various types of logbook entries.</p>"},{"location":"userguide.html#elog-command-line-client","title":"elog command line client","text":"<p>In addition to submission of logbook entries through the Web interface, the standalone \"client\" program <code>elog</code> can be used.</p> <p>The parameters are:</p> <pre><code>elog <parameters>\n\n -h <hostname> Hostname where elogd is running\n [-p port] Port where elogd is running\n [-d subdir] URL Directoy where elogd is running\n -l logbook Name of logbook\n -s Use SSL for communication\n [-v] For verbose output\n [-w password] Write password defined on server\n [-u username password] User name and password\n [-f <attachment>] Up to 50 attachments\n -a <attribute>=<value> Up to 50 attributes\n [-r <id>] Reply to existing message\n [-q] Quote original text on reply\n [-e <id>] Edit existing message\n [-x] Suppress email notification\n [-n 0|1|2] Encoding: 0:ELcode,1:plain,2:HTML\n -m <textfile>] | <text>\n</code></pre> <p>Arguments with blanks must be enclosed in quotes. The elog message can either be submitted on the command line, piped in like</p> <p><code>cat text | elog -h ... -l ... -a ...</code></p> <p>or in a file with the -m flag. Multiple attributes and attachments can be supplied. If attributes with multiple possible values are defined in a logbook (via the \"MOptions\" keyword), they can be separated with a \"|\", like <code>-a \"<attribute>=<value1> | <value2>\"</code>. The message text can be supplied directly at the command line or submitted from a file with the <code>-m</code> flag.</p> <p>The <code>elog</code> program makes it possible to submit logbook entries automatically by the system or from scripts. In some shift logbooks this feature is used to enter alarm messages automatically into the logbook.</p>"},{"location":"userguide.html#rss-feed","title":"RSS Feed","text":"<p>RSS (RDF Site Summrary or Really Simple Syntication) is a web feed format to publish frequently new or updated ELOG entries. This is a bit like the email notifications present in ELOG, but the RSS system does not go through an email reader, but through a dedicated RSS reader. This helps to seperate ELOG updates form other email or spam. An RSS \"channel\" can be subscribed to, so one gets notified whenever a new or updated entry exists. One can either use a dedicated RSS reader or aggregator, or use the RSS functionality of a web browser, such as Firefox or Google Reader.</p> <p>To obtain the RSS feed, one simply has to request the file <code>elog.rdf</code> from a logbook. For the ELOG forum, one can enter the URL</p> <p><code>https://elog.psi.ch/elogs/Forum/elog.rdf</code></p> <p>The browser then offers the possiblity to subscribe to that logbook:</p> <p></p> <p>In case of \"Live Bookmarks\" in Firefox, new logbook entries automatically appear in the bookmark list:</p> <p></p> <p>Standalone RSS reader can also notify the user of new entries with dialog boxes and sounds. For a list of availabel RSS aggregators, see here.</p>"},{"location":"wishlist.html","title":"ELOG Wishlist","text":"<p>Here are some \"wishlist\" items requested by users. I will work down the list as time permits, starting at the items with the most votes. You can vote for a feature, or suggest one, by sending me an email.</p> Feature Votes Implement groups of users 8 Password expiration 2 Account expiration 1 Make attributes which whould be displayed selectable in \"Find\" page 1 Convert elog text files into XML files and comma separated files with elconv 1 Implement multi-line attributes 8 Derive attribute options from list of entries of another logbook 1 Specify date format explicitly for substitutions, like $entry date{%Y} 2 Change attributes of whole thread, like mark a thread \"open\" or \"closed\" 4 Automatic unlocking of entries after a specific time period 1 Implement attributes which are math results from others, like att3=att1+att2 3 Show sums of numeric attributes 2 Let each user choose its language separately 1 Implement multiple selection boxes 1 Select individual columns for display and printing 2 \"Incremental\" options. Have fixed set of global options, and in eachlogbook add or remove some of those with+Options = ... or -Options = ... 1 \"Include\" statement for config file. 2 Use different styles (colors) depending on an attribute 1 Add native IPv6 support 1 Copy new elog entries automatically to other logbooks 1 Extend the search facility to (text) attachments 1"}]} |