1ELOGD(8)                    System Manager's Manual                   ELOGD(8)
2
3
4

NAME

6       elogd - web server program for Electronic Logbook ELOG
7

SYNOPSIS

9       elog  [ -C url ] [ -c file ] [ -D ] [ -d directory ] [ -f file ] [ -k ]
10       [ -l logbook ] [ -M ] [ -m ] [ -n hostname ] [ -p port ] [ -S  ]  [  -s
11       directory ] [ -v ] [ -x ]
12
13

DESCRIPTION

15       The  Electronic Logbook ELOG can be used to store and retrieve messages
16       through a Web interface. Depending on the configuration, the ELOG  sys‐
17       tem can host one or more logbooks which are stored in separate sections
18       on the server.  elogd is the daemon program serving  as  a  simple  web
19       server for the ELOG system.
20

OPTIONS

22       elogd accepts the following options:
23
24       -C url clone remote elogd configuration
25
26       -c file
27              specify configuration file
28
29       -D     become a daemon
30
31       -d directory
32              specify logbook root directory
33
34       -f file
35              specify PID file
36
37       -M     synchronize with removing deleted entries
38
39       -m     synchronize logbook(s) with remote server
40
41       -n host
42              host where elogd will run
43
44       -k     do not use keep-alive
45
46       -l logbook
47              specify logbook for `-r' and `-w' commands
48
49       -p port
50              port where elogd will run
51
52       -S     be silent
53
54       -s directory
55              specify resource directory (eg. themes, icons)
56
57       -v     debugging output
58
59       -x     enable  execution  of  shell commands (unless compiled with this
60              feature)
61

SEE ALSO

63       elog(1).
64
65       The full documentation for ELOG is maintained as an  html  manual.  You
66       can reach it from the package document directory.
67

WARNINGS

69       elogd  is  run under a separate user/group elog , by default. You might
70       change it via Usr and Grp options in configuration file. The configura‐
71       tion and stylesheet files should be readable by that user.
72
73       Passwords are transferred over the network in plain text and therefore,
74       are not secure. So if passwords are used elogd should be  started  with
75       the SSL option in the configuration file for secure connections.
76

AUTHOR

78       Written by Stefan Ritt <stefan.ritt@psi.ch>.
79
80       This  manual  page  was written by Recai Oktas <roktas@omu.edu.tr>, for
81       the Debian GNU/Linux system (but may be used by others).
82
83
84
85                               January 15, 2003                       ELOGD(8)