[Nut-upsdev] [Nut-upsuser] Failed to connect to parent

Charles Lepple clepple at gmail.com
Wed Jun 13 01:18:16 UTC 2007

On 6/12/07, Arjen de Korte <nut+devel at de-korte.org> wrote:
> Roger Price wrote:
> >>> CMDSCRIPT /usr/sbin/upssched-cmd
> >>> PIPEFN /var/state/ups/upssched.pipe
> >>> LOCKFN /var/state/ups/upssched.lock
> >> Is /var/state/ups owned and writeable by the NUT user?
> >> Have the pipe and lock files been created?
> > That was the problem.  openSUSE uses /var/run for such run-time data, not
> > /var/state.
> Can't we create some autoconf magic, so that the defaults that are
> configured in the sample configuration files will match the configure
> option --with-statepath=<whatever>? In that case, merely uncommenting
> the default would be enough.


The only catch is that the user would still have to create the
upssched subdirectory. I suppose we could change that, since very few
people will be running NUT with the split-userid arrangement proposed
by Russell.

- Charles Lepple

More information about the Nut-upsdev mailing list