2009/9/8 Chris Abel <[email protected]> > I did manage to get tripplite_usb and upsdrvctl working with different > tags in ./configure, but I still do not think it is correct. This is my > output for tripplite_usb -DDDDD -a ups1: > Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.4.1) > Warning: This is an experimental driver. > Some features may not function correctly. > > send_to_all: SETINFO driver.parameter.port "auto" > debug level is '5' > Can't chdir to /var/run/nut --with-altpidpath=/var/run/nut: No such file > or directory > > This is my output for upsdrvctl start: > Network UPS Tools - UPS driver controller 2.4.1 > Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.4.1) > Warning: This is an experimental driver. > Some features may not function correctly. > > Can't chdir to /var/run/nut --with-altpidpath=/var/run/nut: No such file > or directory > Driver failed to start (exit status=1) > > It seems that whenever I specify a different directory in a ./confgure tag > it does not get applied right. > > Thanks for helping thus far. > > part of the debian process here: mkdir /var/run/nut && chgroup nut /var/run/nut
it's quite possible that the nut user has been removed. if so: addgroup --quiet --system nut adduser --quiet --system --ingroup nut --home /var/lib/nut --no-create-home nut then relaunch the driver... cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/
_______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
