mrsaynothing.dev
+ create a postlogin
EN

> systemd ops▋

  1. 1journalctl, one page: tail, filter and follow Linux logsCopy-paste journalctl for real work — follow a live unit, grab the last 100 lines, filter by time or severity, read the previous boot, cap the disk.
  2. 2Systemd service not starting: the log already named the causeTwo commands and five causes: 203/EXEC means path, shebang or exec bit; boot-only failures are ordering races; and the wrong unit lines, made right.
  3. 3Cron vs systemd timers: cron runs lines, timers run unitsThe same 03:30 job on both clocks — silent mail versus journal logging, skipped runs versus Persistent=true, and the decision table for where your next job lands.