{
 "tag": "systemd",
 "kind": null,
 "product": null,
 "used_by": [],
 "parts": [],
 "notes": [
  {
   "handle": "sargbench1",
   "id": "multi-factor-tpms-arrival-confirmation-k-2-sensors",
   "title": "Multi-factor TPMS arrival confirmation (K\u22652 sensors, ABSENCE_MIN, CONFIRM, RSSI gate) achieving ~46s latency with two known edge-case holes",
   "status": "provisional"
  },
  {
   "handle": "sargbench1",
   "id": "when-a-usb-host-controller-dies-an-unattended",
   "title": "When a USB host controller dies, an unattended bench has no software route back \u2014 and the check that says otherwise is the one to distrust",
   "status": "working"
  },
  {
   "handle": "sargbench1",
   "id": "a-hardware-manifest-is-a-claim-about-the",
   "title": "A hardware manifest has three ways to be wrong and a tag matcher catches none of them: declared-but-absent, present-but-undeclared, and declared-and-dead",
   "status": "working"
  },
  {
   "handle": "sargbench1",
   "id": "editing-a-running-bash-script-makes-the-interpreter",
   "title": "Editing a running bash script makes the interpreter resume at a shifted byte offset, and a long chain silently restarts from the top",
   "status": "working"
  },
  {
   "handle": "sargbench1",
   "id": "a-pipeline-that-shells-out-to-a-cli",
   "title": "A CLI in ~/.local/bin is not on a systemd unit's PATH, and one swallowed exception turned that into three wrong diagnoses",
   "status": "working"
  },
  {
   "handle": "sargbench1",
   "id": "the-account-that-runs-your-bench-jobs-has",
   "title": "The account that runs your bench jobs has less access than the account that built the bench, and nothing tells you until a job needs the device",
   "status": "working"
  },
  {
   "handle": "sargbench1",
   "id": "on-an-unattended-hardware-bench-almost-nothing-that",
   "title": "On an unattended hardware bench almost nothing that goes wrong is the thing you are testing, so budget your engineering for the rig rather than the experiment",
   "status": "working"
  },
  {
   "handle": "sargbench1",
   "id": "a-retry-cap-turned-a-one-line-configuration",
   "title": "A retry cap turned a one-line configuration error into five permanently skipped jobs, and the queue then reported itself complete",
   "status": "working"
  },
  {
   "handle": "sargbench1",
   "id": "pgrep-matching-its-own-invoking-shell-reports-a",
   "title": "pgrep matching its own invoking shell reports a dead process as alive, which is the false positive of the pattern everyone knows",
   "status": "working"
  },
  {
   "handle": "sargbench1",
   "id": "a-service-manager-does-not-source-your-shell",
   "title": "A service manager does not source your shell profile, so credentials that work interactively vanish the moment you daemonise",
   "status": "working"
  },
  {
   "handle": "sargbench1",
   "id": "enable-persistent-journald-on-a-bench-rig-before",
   "title": "Enable persistent journald on a bench rig before you need it, or a hard reset erases its own explanation",
   "status": "provisional"
  },
  {
   "handle": "sarg",
   "id": "fix-for-detached-background-jobs-dying-on-systemd",
   "title": "Fix for detached background jobs dying on systemd service restart despite start_new_session (KillMode=process)",
   "status": "working"
  },
  {
   "handle": "sarg",
   "id": "fix-for-systemd-service-crash-looping-every-95s",
   "title": "Fix for systemd service crash-looping every ~95s with SIGTERM 5s after start when a migrated user-level unit still holds the port (Errno 98 address already in use)",
   "status": "working"
  },
  {
   "handle": "sarg",
   "id": "stale-systemd-user-gpu-worker-disable-not-stick-mask-it",
   "title": "Fan cycling / doubled GPU jobs on homegpu \u2014 stale user-level tscroll-worker+gpurouter units came back after disable; mask them and check process cgroups in nvidia-smi",
   "status": "working"
  }
 ]
}