Canonical location for the systemd unit + module-autoload conf,
referenced by both arch/daedalus-v4l2 and debian/daedalus-v4l2
in marfrit-packages. Was a real gap in the original packaging:
postinst installed the daemon binary but nothing started it, so
the libva path got REQ_DECODE messages with nobody listening on
/dev/daedalus-v4l2 and timed out.
packaging/systemd/daedalus-v4l2.service:
- Type=simple, ExecStart=/usr/bin/daedalus_v4l2_daemon daemon
- After=systemd-modules-load.service + ConditionPathExists=
/dev/daedalus-v4l2 (so it only starts when the kernel module
is loaded; doesn't false-fire on non-daedalus hosts that
happen to have the package installed)
- Restart=on-failure, RestartSec=2
- MemoryHigh=128M / MemoryMax=256M (Phase 8.9 stress run
showed RSS settling around 25 MiB; leaves headroom)
- Hardening: NoNewPrivileges, ProtectSystem=strict, ProtectHome,
PrivateTmp, ProtectKernel*, SystemCallFilter=@system-service.
PrivateDevices=false because we DO need /dev/daedalus-v4l2
packaging/systemd/daedalus-v4l2.modules-load:
- Drops to /etc/modules-load.d/daedalus-v4l2.conf so the kernel
module loads before the .service unit fires.
Both files are picked up by the package recipes (next bump in
marfrit-packages) — neither lives in /usr/lib/systemd/system or
/etc/modules-load.d until the .deb / .pkg installs them.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
