Re: Victor Echolot Pinger [operational again]
Johann 'Myrkraverk' Oskarsson <[email protected]>
| Newsgroups | alt.privacy,alt.privacy.anon-server,alt.cypherpunks |
|---|---|
| Organization | Watcom Pro Ltd. |
| Message-ID | <[email protected]> |
On 07/08/2026 7:41 PM, Gabx wrote: > The Echolot pinger at *VICTOR* echolot.virebent.art > (https://echolot.virebent.art) is operational again. > > The outage was caused by a stale PID file left behind . The PID file now > lives under /run, preventing it from surviving reboots. > > The systemd service was also improved with proper network ordering, an > explicit working directory, and automatic restart on failure. > > best regards > > Gabx > > --- Digital Signature --- > q07/u5Qi6Fqlk2tG8SONB5qO7rDtiCVqYIdVdTsItdZcgogoCr9k3y7NyFZ88Cy2bvDrw1nbHPTbcvEpHxxADQ== > That sounds like it's made by inexperience programmers. It's much better to flock() the pidfile, and then it doesn't matter if there's a stale one left behind. The locking will just succeed. -- Johann | email: invalid -> com | http://www.myrkraverk.com/blog/ I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;