search for: altpidpath

...ependent data [PREFIX/com] --localstatedir=DIR modifiable single-machine data [PREFIX/var] --runstatedir=DIR modifiable per-process data [LOCALSTATEDIR/run] --with-statepath=PATH path for ups state files (${STATEPATH}, typically /var/state/ups) --with-altpidpath=PATH path for NUT driver/upsd .pid files not running as root (<statepath>) --with-pidpath=PATH Path for root-owned .pid files (${PIDPATH}, typically /var/run) 2) There are some issues; the defaults are hardcoded paths instead of fol...

...an not compromise important stuff - say, replace `upsmon.pid` with a content of `1` so the next `upsmon -c command` might signal `init` and bring down or otherwise confuse the OS). As such, daemons that start as not-root or drop privileges early can not create their PID or socket files there. * The ALTPIDPATH as commented is for PIDs of non-root daemons (since recently it is also checked for root daemons as a fallback, I think). * The STATEPATH is a historic misnomer: a long time ago drivers wrote their state regularly into a dedicated file which upsd then had regularly read to post data updates. This w...

> Also the upsmon POWERDOWNFLAG fits into this question I'm confused. That flag can't be persistent across reboots, can it?

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.

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.

>> Also the upsmon POWERDOWNFLAG fits into this question > I'm confused. That flag can't be persistent across reboots, can it? Well, there is little practical reason, if any, for an `/etc/killpower` (as it is commonly named) to exist when you boot. It also has a potential for confusion if not deleted, as we discovered in some recent discussion - e.g. due to no packaged NUT init

I am running tests on my system and UPS, making sure that it is reliably able to come up, detect power loss, shutdown safely, and then come back up when the power returns. It does that MOST of the time. However, a significant part of the time, the system comes up, and then doesn't respond to loss of power. Doing some checking, I find that the reason is because upsd never started. Capturing

...does not. In the configuration.txt file, there is one section: Directories used by NUT at run-time ----------------------------------- --with-pidpath=PATH Changes the directory where pid files are stored. By default this is /var/run. Certain programs like upsmon will leave files here. --with-altpidpath=PATH Programs that normally don't have root powers, like the drivers and upsd, write their pid files here. By default this is whatever the statepath is, as those programs should be able to write there. --with-statepath=PATH Change the default location of the state sockets created by the dri...

Model: Tripp-lite OMNIVS1500 Error: Network UPS Tools - UPS driver controller 2.2.1- Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.11 (2.2.1-) Warning: This is an experimental driver. Some features may not function correctly. Detected a UPS: unknown/unknown libusb_set_report() returned -1 instead of 8 Could not reset watchdog. Please send model information to nut-upsdev mailing

...ng is that the PID file is left over from the last test, and another process got that PID instead. Due to history and conflicting requirements, the path selection is not as simple as it could be. From ./configure --help: --with-statepath=PATH path for ups state files (/var/state/ups) --with-altpidpath=PATH path for driver/upsd .pid files (<statepath>) [...] --with-pidpath=PATH path for .pid files (/var/run) You might not want to use the default for --with-altpidpath: /var/state/* is not generally cleared at boot time, whereas /var/run is either wiped or mounted on a RAM filesystem....

...ut".) > > For the upsd issue, check your state path and pid paths (also options to > ./configure). > Sorry, I should have clarified this. My configure options were: ./configure --with-user=nut --with-group=dialout --with-statepath=/var/run/ nut --with-pidpath=/var/run/nut --with-altpidpath=/var/run/nut --sysconfdir=/ etc/ups --with-drvpath=/sbin --with-all --with-pkgconfig-dir=/usr/lib/ pkgconfig --disable-static --without-ipv6 mostly ripped from the Fedora 12 2.4.1 specfile. I'm pretty sure the --with-user=nut options is in effect since I instrumented libusb_get_report to print...

...ng if what I have done is good : # get the source from github on my computer # autogen.sh # name=nut # ./configure --prefix=/ --sysconfdir=/etc/$name --mandir=/usr/share/man --libdir=/usr/lib --includedir=/usr/include --datadir=/usr/share/$name --with-statepath=/var/run/nut --with-altpidpath=/var/run/nut --with-drvpath=/lib/nut --with-pidpath=/var/run/$name --with-user=$name ?with-group=$name --without-ssl There was an error : ./configure: line 7079: syntax error near unexpected token `CPPUNIT,' ./configure: line 7079: `PKG_CHECK_MODULES(CPPUNIT, cppunit, have_cppun...

...sr/ports/sysutils/nut/Makefile: STATEDIR?= /var/db/nut [...] CONFIGURE_ARGS= --sysconfdir=${PREFIX}/etc/nut \ --program-transform-name="" \ --localstatedir=${STATEDIR} \ --datadir=${PREFIX}/etc/nut \ --with-drvpath=${PREFIX}/libexec/nut \ --with-statepath=${STATEDIR} \ --with-altpidpath=${STATEDIR} \ --with-pidpath=${STATEDIR} \ --with-pkgconfig-dir=${PREFIX}/libdata/pkgconfig \ --with-user=${NUT_USER} \ --with-group=${NUT_GROUP} \ --with-dev I think you need to re-run ./configure in the source tree with the driver, using the arguments above. Then 'cd drivers; make...

...: > # get the source from github on my computer > # autogen.sh > # name=nut > # ./configure --prefix=/ --sysconfdir=/etc/$name --mandir=/usr/share/man > --libdir=/usr/lib --includedir=/usr/include --datadir=/usr/share/$name > --with-statepath=/var/run/nut --with-altpidpath=/var/run/nut > --with-drvpath=/lib/nut --with-pidpath=/var/run/$name > --with-user=$name ?with-group=$name --without-ssl If these are the same parameters as are used to build the .deb, then that should owrk. > There was an error : > ./configure: line 7079: syntax error near une...

- Charles > On Oct 16, 2016, at 3:34 AM, Daniel Shields <grungelizard9 at hotmail.com> wrote: > > I've been testing with debug further and there's a few extra lines when the nut-server stops communicating as opposed to when it's running. > > > Backtrace after stale data, UPS nailbunny at localhost is unavailable: > Sorry to take a while to get back to you

...--sysconfdir=/etc/nut --localstatedir=/var \ --libexecdir=/usr/lib/nut --srcdir=. --disable-maintainer-mode \ --disable-dependency-tracking --disable-silent-rules --libdir=/usr/lib/x86_64-linux-gnu \ --with-ssl --with-nss --with-cgi --with-dev --enable-static \ --with-statepath=/var/run/nut --with-altpidpath=/var/run/nut \ --with-drvpath=/lib/nut --with-cgipath=/usr/lib/cgi-bin/nut \ --with-htmlpath=/usr/share/nut/www --with-pidpath=/var/run/nut \ --datadir=/usr/share/nut --with-pkgconfig-dir=/usr/lib/aarch64-linux-gnu/pkgconfig \ --with-user=nut --with-group=nut --with-udev-dir=/lib/udev \ --with-syst...

Thank You for You reply, Charles D?a 07.10.2017 o 14:30 Charles Lepple nap?sal(a): > Is the "lan4.1" cable different from this one? > http://networkupstools.org/cables.html#_tripp_lite Yes, it is different. The correct cable for this interface version looks like this: http://pinouts.ru/UPS/tripplite_smartpro_cable_pinout.shtml > Are you comfortable with rebuilding the

....h --with-udev-dir=/lib/udev \ --prefix=/usr \ --exec-prefix=/ \ --sysconfdir=/etc/nut \ --mandir=/usr/share/man \ --libdir=/lib \ --includedir=/usr/include \ --without-ssl \ --with-dev \ --enable-static \ --with-statepath=/var/run/nut \ --with-altpidpath=/var/run/nut \ --with-drvpath=/lib/nut \ --with-htmlpath=/usr/share/nut/www \ --with-pidpath=/var/run/nut \ --datadir=/usr/share/nut \ --with-pkgconfig-dir=/usr/lib/pkgconfig \ --with-user=nut --with-group=nut I get this when I run upsdrvctl start Detected LiebertPS...

...localstatedir=/var \ > --libexecdir=/usr/lib/nut --srcdir=. --enable-maintainer-mode \ > --disable-silent-rules --libdir=/usr/lib/x86_64-linux-gnu \ > --with-ssl --with-nss --with-cgi --with-dev --enable-static \ > --with-statepath=/var/run/nut --with-altpidpath=/var/run/nut \ > --with-drvpath=/lib/nut --with-cgipath=/usr/lib/cgi-bin/nut \ > --with-htmlpath=/usr/share/nut/www --with-pidpath=/var/run/nut \ > --datadir=/usr/share/nut --with-pkgconfig-dir=/usr/lib/x86_64-linux-gnu/pkgconfig \ > --with-user=nut -...

Hi Arnaud & Charles, You?ll have to forgive my low level of Linux Understanding here?. I downloaded the source files, modified the appropriate driver file, re-compiled it (all of this was a lot of research and learning!) When I use the new driver I get ? Network UPS Tools - UPS driver controller 2.7.2 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.93 (2.7.4.1) Can't chdir to