lightsystemdarkgreen
raw
current commit
261119.1 · The project is dirview and its command drvu

Log

drvu logs every action, always. There is no flag and no level to set, because a filter set before a mistake drops the entry that would explain it.

Entries go to the systemd journal, tagged drvu:

journalctl --user -t drvu --since -1h
journalctl --user -t drvu DRVU_ENDPOINT=127.31.1.1-80
journalctl --user -t drvu -p err

Each entry carries the endpoint it concerns in DRVU_ENDPOINT and its priority in PRIORITY: 3 for faults, 6 for the rest. The journal also holds what explains a vanished server, such as a suspend, an OOM kill or a logout.

Where no journal socket exists, entries go to ~/.local/state/drvu/log instead, or below $XDG_STATE_HOME when set. Its lines hold time, PID, endpoint, priority and the message. The file is mode 600 and rotates once to log.1 at 1 MB. drvu --help names the place in use.

What is logged

Privacy

A secret share’s token never reaches the log. Paths do, and on shares so do visitors’ addresses.

Your user journal is readable by you and by members of adm and systemd-journal.