Experiments, lessons, and practical guides from running Linux services and personal infrastructure at home.
A process can still have a PID, consume little CPU, and appear as active (running) while its useful work has stopped. Its event loop may be blocked, a worker may be waiting forever, or one internal lock may prevent every request from progressing. A restart ru…
Read article
A service can be absent from the process list while its address is already listening. That sounds contradictory only if the daemon must own…
A small service needs somewhere to put a Unix socket, a database, downloaded metadata, and perhaps its own log files. Creating one writable…
There is a version of this question that sounds obvious and is not: HTTP/3 has been a published IETF standard since June 2022, most browser…
A service starts during boot, tries to contact a remote endpoint, and fails because the machine has not finished acquiring an address. Addi…
A job is scheduled every five minutes, but one run occasionally needs six. When the next trigger arrives, should it start a second copy, wa…
A Debian server can keep running after a configuration change and still leave an awkward question for later: what exactly changed? Perhaps …
A service cannot append to its database, a backup stops halfway, or an application logs No space left on device. The obvious explanation is…
A long-running service on a home server exits at 3 a.m. Should the machine leave it down, restart it immediately, or keep trying until morn…
A home server can display the right hour and still have an unreliable clock. The timezone may be correct while network synchronization is f…
