[Nut-upsdev] pidpath, altpidpath, statepath considered muddled or confusing

[Jim Klimov]

Sorry for not being clear enough :)

I meant that as there are several volatile path related settings, typically
those pid/state ones are considered and discussed (this is not the first
time such question is raised).

But there is also e.g. `--with-powerdownflag=...` (for build-time default),
or the end-users' choice of the setting in their `upsmon.conf` files, which
fits this general subject of volatile data that NUT can write/read during
run time, so there are certain permission and persistence aspects to it too.

Jim


On Tue, May 20, 2025 at 1:06 PM Greg Troxel via Nut-upsdev <
nut-upsdev at alioth-lists.debian.net> wrote:

> Edgar Fuß via Nut-upsdev <nut-upsdev at alioth-lists.debian.net> writes:
>
> > I had read the "Also the upsmon POWERDOWNFLAG fits into this question"
> > in your response as you meant the flag belonged in the persistent
> > state directory.
>
> I didn't 100% follow what Jim thinks.  I think it belongs in
> /var/run-ish-root.
>
> _______________________________________________
> Nut-upsdev mailing list
> Nut-upsdev at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20250520/dc503cfb/attachment.htm>