ELOG(1)

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

πŸ’– ELOG(1) β€” the elog girlies' manual πŸ’–

okay so this is the page for elog, from the General Commands Manual section of your friendly neighbourhood man pages, bestie. it's the standalone client for the Electronic Logbook and it is lowkey iconic. let's get into it ✨


✨ NAME ✨

elog β€” utility program for Electronic Logbook ELOG πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

elog -a attribute=value [ -e id ] [ -f file... ] -h host [ -l logbook ]
[ -m textfile ] [ -p port ] [ -r id ] [ -s subdir ] [ -u username
password ] [ -v ] [ -w password ] message  [ -x ]

🌸 DESCRIPTION 🌸

so basically the Electronic Logbook ELOG is this whole thing where you store and retrieve messages through a Web interface. depending on how it's configured, the ELOG system can host one or more logbooks, and those logbooks live in separate sections on the server. it's giving organized. it's giving separate sections. πŸ’…

elog is the standalone client program β€” the one you run from the command line β€” and its whole job is interacting with the ELOG daemon, elogd. no cap. 🫢

now, your message? you've got options, bestie:

  • you can submit it right there on the command line,
  • you can pipe it through stdin,
  • or you can put it in a file and use the -m flag.
heads up: in that first case β€” command line message β€” if your message has blanks in it, you must wrap it in quotes. literally non-negotiable. 😭

you can specify multiple attributes and also several attachments, because why settle. and the password you give has to match the write password that's defined on the server. periodt.

and if user level access is defined on the server (via the Password file option), then you need to hand over a valid user name / password pair using the -u option. that's the vibe check right there. πŸ”₯

the elog program is what makes it possible to submit logbook entries automatically β€” by the system, or from scripts. in some shift logbooks this feature gets used to enter alarm messages automatically into the logbook. main character automation energy honestly. πŸ‘‘


πŸ’… OPTIONS πŸ’…

elog accepts the following options, babes:

  • -a attribute=value β€” set attribute to value 🌈
  • -e id β€” edit existing message of id ✏️
  • -f file... β€” attach files while submitting πŸ“Ž
  • -h host β€” host where elogd is running πŸ–₯️
  • -l logbook β€” name of logbook or experiment πŸ““
  • -m textfile β€” submit message from textfile πŸ“
  • -p port β€” port where elogd is running πŸ”Œ
  • -r id β€” reply to existing message of id ↩️
  • -s dir β€” directory where logbooks reside πŸ“
  • -u username password β€” username and password πŸ”
  • -v β€” verbose output πŸ—£οΈ
  • -w password β€” write password defined on server πŸ—οΈ
  • -x β€” suppress email notification 🀫

⭐ SEE ALSO ⭐

elogd(8).

the full documentation for ELOG is maintained as an html manual. you can reach it from the package document directory. go read it, bestie, it's right there. πŸ“š


πŸ’œ 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). 🫢


and that's the whole page, no notes. this one's dated January 15, 2002 and it lives in the ELOG(1) section β€” so like, respect the elders, they ate. πŸ’–βœ¨πŸŽ€πŸ¦‹πŸŒΈπŸ’…πŸ‘‘

πŸ“¦ where this page comes from