ELOGD(8)

πŸ“¦ version 3.1.3-1, in ubuntu jammy

✨ 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 remote elogd configuration. 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 where elogd will run.
  • -k β€” do not use keep-alive.
  • -l logbook β€” specify the logbook for the -r and -w commands.
  • -p port β€” port where elogd will 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