[Nut-upsuser] NUT no longer works after 2.7 -> 2.8 upgrade

[Jim Klimov]

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 <jimklimov+nut at gmail.com> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20221201/9b1846de/attachment.htm>