Spawning a New Process for Socket-Activated Daemons is Error-Prone

I recently debugged a mysterious latency issue: after migrating a systemd service from path-activation to socket-activation, there was a consistent ~1 second time-to-available latency. The culprit was a bad practice—starting the daemon program as a new process in socket-activation. Let's dive into the details. Starting soci-snapshotter On-Demand Using Socket Activation soci-snapshotter is an…