From d8b7e3817eeed7773f3721b9d757588cf373b853 Mon Sep 17 00:00:00 2001 From: Stefan Ritt Date: Mon, 7 Apr 2003 13:08:36 +0000 Subject: [PATCH] Added note about admin user SVN revision: 475 --- doc/config.html | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/doc/config.html b/doc/config.html index 6f9969eb..f2450664 100755 --- a/doc/config.html +++ b/doc/config.html @@ -890,8 +890,10 @@ for example, makes the password expire after one day.

The Admin user = <user list> is a list of one or more user names, which have admin rights. They see a button Change elogd.cfg on the -config page by which they can edit elogd.cfg through the web. They can also modify other -users on the Config page, change their passwords or remove them.

+config page by which they can edit elogd.cfg through the web. They can also modify other +users on the Config page, change their passwords or remove them. In +addition, the admin user(s) can delete or edit entries from other users if +Restrict edit = 1.

The Login user = <user list> 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 @@ -903,7 +905,7 @@ section in the configuration file. Only those users listed in this statement can 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 +valid for all logbooks. If there would be individual logbook password files, one would have to change the password in all logbooks individually.