One of the bigger problems with that, is that I rely on the systemd Journal a lot, including the fact that services started will have their stdout available in the journal.
If I abandon systemd, I'll have to come up with something similar for shepherd (if it doesn't already have something like that - I haven't finished reading the manual yet), because just logging to stdout is mighty convenient. I'm not parting with that luxury.
@algernon didn't /dev/log expect syslog format though? IIRC the pre-systemd way was to pipe stdout/stderr to logger(1) with options for severity, facility etc. but I haven't done this myself and I don't know how feasible that'd be with shepherd....
@algernon oh, also, getting a PID through SO_PEERCRED and then looking up properties of that process in /proc/$pid is race-y, but I guess for the purpose of logs it isn't that big of a problen
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!