EVENTLOGADM(8)

👑 EVENTLOGADM(8) — the manual page, bestie edition

okay so this is eventlogadm, from the System Administration tools corner of the manual. Strap in, we're putting records into the Samba event log store and it's gonna be adorable. 💖

---

✨ NAME ✨

eventlogadm — push records into the Samba event log store 🫶

---

🌸 SYNOPSIS 🌸

eventlogadm [-s] [-d] [-h] -o addsource EVENTLOG SOURCENAME MSGFILE

eventlogadm [-s] [-d] [-h] -o write EVENTLOG

eventlogadm [-s] [-d] [-h] -o dump EVENTLOG RECORD_NUMBER

---

🦋 DESCRIPTION 🦋

This tool is part of the samba(1) suite. yes, that suite. iconic behavior. 💅

eventlogadm is a filter. It takes formatted event log records on standard input and writes them straight into the Samba event log store. That's it, that's the whole vibe. 🎀

And then — the way this works — a Windows client can manipulate those records using the usual administration tools. no cap. ✨

---

🔥 OPTIONS 🔥

• -s FILENAME — the -s option makes eventlogadm load the configuration file you hand it as FILENAME, instead of the default one Samba would normally use. glow up via custom config, basically. 🌈
• -d — the -d option makes eventlogadm emit debugging information. it's giving "tell me everything, bestie". 💜
• -o addsource EVENTLOG SOURCENAME MSGFILE — the -o addsource option creates a new event log source. brand new source, fresh out the box. 🎀
• -o write EVENTLOG — the -o write reads event log records from standard input and writes them to the Samba event log store named by EVENTLOG. 📥
• -o dump EVENTLOG RECORD_NUMBER — the -o dump reads event log records from a EVENTLOG tdb and dumps them to standard output on screen. show me everything, fr fr. 👀
• -h — print usage information. help me help you. 🙈

---

🧚 EVENTLOG RECORD FORMAT 🧚

for the write operation, eventlogadm expects to be able to read structured records from standard input. These records are a sequence of lines, with the record key and data separated by a colon character. Records are separated by at least one or more blank line. 🍓

The event log record field are: (yes that's the original phrasing, we keep it, we love it)

• LEN — This field should be 0, since eventlogadm will calculate this value. let it do the math, she's good at it. 🌸
• RS1 — This must be the value 1699505740. literally must. 👑
• RCN — This field should be 0.
• TMG — The time the eventlog record was generated; format is the number of seconds since 00:00:00 January 1, 1970, UTC.
• TMW — The time the eventlog record was written; format is the number of seconds since 00:00:00 January 1, 1970, UTC.
• EID — The eventlog ID.
• ETP — The event type — one of "INFO", "ERROR", "WARNING", "AUDIT SUCCESS" or "AUDIT FAILURE". pick your fighter. 💀
• ECT — The event category; this depends on the message file. It is primarily used as a means of filtering in the eventlog viewer.
• RS2 — This field should be 0.
• CRN — This field should be 0.
• USL — This field should be 0.
• SRC — This field contains the source name associated with the event log. If a message file is used with an event log, there will be a registry entry for associating this source name with a message file DLL.
• SRN — The name of the machine on which the eventlog was generated. This is typically the host name. hi hostname bestie. 🎀
• STR — The text associated with the eventlog. There may be more than one string in a record.
• DAT — This field should be left unset. leave it alone. 🙈

---

💅 EXAMPLES 💅

An example of the record format accepted by eventlogadm:

LEN: 0
RS1: 1699505740
RCN: 0
TMG: 1128631322
TMW: 1128631322
EID: 1000
ETP: INFO
ECT: 0
RS2: 0
CRN: 0
USL: 0
SRC: cron
SRN: dmlinux
STR: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly)
DAT:

Set up an eventlog source, specifying a message file DLL:

eventlogadm -o addsource Application MyApplication | \\
     %SystemRoot%/system32/MyApplication.dll

Filter messages from the system log into an event log:

tail -f /var/log/messages | \\
     my_program_to_parse_into_eventlog_records | \\
          eventlogadm SystemLogEvents

look at that pipeline. she's eating. 🔥

---

💜 VERSION 💜

This man page is part of version 4.24.7-Ubuntu-4.24.7+dfsg-1ubuntu1 of the Samba suite.

---

🌟 AUTHOR 🌟

The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. legacy behavior, we respect it deeply. 👑

---

and that's the whole page, bestie!! 🫶 this little slice of the Samba suite ships as part of Samba 4.24.7-Ubuntu-4.24.7+dfsg-1ubuntu1, dated 09/13/2026 — same manual, section 8, same everything, just way more fun to read now. mwah. 💖✨🎀