Displaying 2 results from an estimated 2 matches for "altpid".
Did you mean:
altid
2025 May 18
1
pidpath, altpidpath, statepath considered muddled or confusing
...e files intended to persist across reboots
/var/run/nut:
- pidfiles
- (probably) sockets
1) configure args slightly confusing autoconf vs nut
nut has configure args in two groups; one setting the usual autoconf
variables not really about nut, and the second group setting state, pid,
altpid:
--sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com]
--localstatedir=DIR modifiable single-machine data [PREFIX/var]
--runstatedir=DIR modifiable per-process data [LOCALSTATEDIR/run]
--with-statepath=PATH path for ups state files (${STATEPATH}, typic...
2025 May 18
1
pidpath, altpidpath, statepath considered muddled or confusing
...an not compromise important
stuff - say, replace `upsmon.pid` with a content of `1` so the next `upsmon
-c command` might signal `init` and bring down or otherwise confuse the
OS). As such, daemons that start as not-root or drop privileges early can
not create their PID or socket files there.
* The ALTPIDPATH as commented is for PIDs of non-root daemons (since
recently it is also checked for root daemons as a fallback, I think).
* The STATEPATH is a historic misnomer: a long time ago drivers wrote their
state regularly into a dedicated file which upsd then had regularly read to
post data updates. Th...