For the sake of cross-referencing, posted an issue at https://github.com/networkupstools/nut/issues/1727
On Thu, Dec 1, 2022 at 7:44 PM Jim Klimov <[email protected]> wrote: > Curious finding up there. I think this is due to `load_upsdconf(0);` > being at > https://github.com/networkupstools/nut/blob/master/server/upsd.c#L1776 > being after the initial signal-probing for competitors (or sending a > command to a running daemon), so using built-in PID/STATE paths, and > notably that probing happens before the optional chrooting (and PID file is > later recorded relative to the chroot). > > For that initial probing, it would honor the NUT_ALTPIDPATH envvar > (although still disregarding "relative to chroot" part if used), but not > yet the know config file contents. > > So it is messed up somewhat. > > FWIW, last week I tried to track down current usage of various PATHs in > the sources, see > https://github.com/networkupstools/nut/issues/1712#issuecomment-1327627850 > if interested :) > > Hope this helps, > Jim Klimov > >
_______________________________________________ Nut-upsuser mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
