diff --git a/doc/adminguide.html b/doc/adminguide.html index 7d1b4da0..759b48d2 100755 --- a/doc/adminguide.html +++ b/doc/adminguide.html @@ -70,6 +70,9 @@ To start the daemon automatically, enter: which will start the daemon on run levels 3,4 and 5 after the next reboot.

+Note that the RPM installation creates a user and group elog, under +which the daemon runs. +

Installation from the tarball:

@@ -92,9 +95,22 @@ The elogd executable can be started manually for testing wit

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 elogd is started a root, or the "sticky bit" is set on +only be used if elogd is started under root, or the "sticky bit" is set on the executable.

+When elogd 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 Usr and +Grp.. If found, elogd uses that user and goupe +name to run under. The names must of course be present on the system (usually +/etc/passwd and /etc/group). If the statements +Usr and Grp. are not present, elogd +tries user and group elog, then the default user and group (normally +nogroup and nobody). Care has to be taken +that elogd, 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 elog. +

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 /sbin/ifconfig program, which must