ELOGD(8)
β¨ ELOGD β¨
okay bestie, welcome to the elogd page β that's the System Manager's Manual entry, section 8, and yes it's giving very demure, very sysadmin. sit down, grab a strawberry, we're learning π
πΈ NAME πΈ
elogd β the web server program for Electronic Logbook ELOG π«Ά
π SYNOPSIS π
elog [ -C url ] [ -c file ] [ -D ] [ -d directory ] [ -f file ] [ -k ] [
-l logbook ] [ -M ] [ -m ] [ -n hostname ] [ -p port ] [ -S ] [ -s
directory ] [ -v ] [ -x ]
(no, the line breaks are not a typo, that's literally how it's written, we do not question the ancestors β¨)
π¦ DESCRIPTION π¦
so the Electronic Logbook ELOG is this whole thing where you store and retrieve messages through a Web interface. it's iconic, it's lowkey the blueprint.
depending on the configuration, the ELOG system can host one or more logbooks, and those logbooks live in separate sections on the server. very organized, very main character energy π
and elogd? that's the daemon program. it's the simple web server that serves the whole ELOG system. periodt.
π OPTIONS π
elogd accepts the following options, and there are fifteen of them, so let's go one by one, no skips, no cuts:
-C urlβ clone a remoteelogdconfiguration. copy her whole fit π§-c fileβ specify the configuration file.-Dβ become a daemon. glow up into the background, babe.-d directoryβ specify the logbook root directory.-f fileβ specify the PID file.-Mβ synchronize with removing deleted entries. yes, actually delete them, not just ghost them π-mβ synchronize logbook(s) with a remote server.-n hostβ host whereelogdwill run.-kβ do not use keep-alive.-l logbookβ specify the logbook for the-rand-wcommands.-p portβ port whereelogdwill run.-Sβ be silent. π€«-s directoryβ specify the resource directory (eg. themes, icons). yes, themes. yes, this is a server with themes. obsessed.-vβ debugging output.-xβ enable execution of shell commands (unless compiled with this feature). > π this one's spicy, more on that below.
π₯ SEE ALSO π₯
the full documentation for ELOG is maintained as an html manual β you can reach it from the package document directory. iykyk π
β οΈ WARNINGS β οΈ
π¨ okay this part is important, bestie, put the phone down and read it.
by default, elogd is run under a separate user/group elog. you might change it via the Usr and Grp options in the configuration file. and listen β the configuration and stylesheet files should be readable by that user. if they aren't, it's not slaying, it's just breaking.
π also: passwords are transferred over the network in plain text and therefore are not secure. fr fr. so if passwords are used, elogd should be started with the SSL option in the configuration file for secure connections. do not skip this one, i am begging π
π AUTHOR π
written by Stefan Ritt <stefan.ritt@psi.ch>.
this manual page was written by Recai Oktas <roktas@omu.edu.tr>, for the Debian GNU/Linux system (but may be used by others). shoutout to both of them, they ate π
and that's the whole page, bestie β¨ this was the ELOGD(8) manual from the System Manager's Manual, last dated January 15, 2003. old money, timeless content, still serving ππ
bye!!
π¦ where this page comes from
- ubuntu jammy: elog 3.1.3-1-1build2 Β· GPL-3.0-or-later WITH OpenSSL exception
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms