similar to: pidpath, altpidpath, statepath considered muddled or confusing

Hi, I looked into this some time back... My reading was that: * The PIDPATH (for root-owned daemons) could be desired in a secured location where only root may write (so unprivileged processes running as `nut`, e.g. random scripts called from upsmon, can not compromise important stuff - say, replace `upsmon.pid` with a content of `1` so the next `upsmon -c command` might signal `init` and bring

>> 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

> 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.

I noticed that many configuration options (configure.txt) have environment variable overrides. However, an important one 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

On Jul 30, 2013, at 10:39 AM, Pavel Potcheptsov (EKTOS) wrote: > Is this a trouble? Driver use path /var/state/ups/ but upsd use path /var/db/nut/upsd.pid Yes, the driver and upsd need to agree on the path to the socket. From the FreeBSD ports tree: /usr/ports/sysutils/nut/Makefile: STATEDIR?= /var/db/nut [...] CONFIGURE_ARGS= --sysconfdir=${PREFIX}/etc/nut \

On Tue, Mar 09, 2010 at 07:14:59PM -0500, Charles Lepple wrote: > On Mar 9, 2010, at 5:54 PM, Kelvin Ku wrote: > >> However, if I try to run usbhid-ups as user "nut", I get: >> >> $ sudo -u nut ./usbhid-ups -a usb > [...] >> Whereas if I run it as root: >> >> $ sudo ./usbhid-ups -a usb -u root > > Did you pass "--with-user=nut"

I?m wondering 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

On Jul 31, 2013, at 9:07 AM, James HORLEY wrote: > I?m wondering 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

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

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

Hi, Just started using NUT with a Liebert PSI-XR 3000 with an Intellislot web card. It seems I can't get it to run properly. I am using NUT 2.6.0 built from source on Ubuntu 8.0.4 . My build parameters are : ./configure --enable-strip --with-linux-hiddev=/usr/include/linux/hiddev.h --with-udev-dir=/lib/udev \ --prefix=/usr \ --exec-prefix=/ \ --sysconfdir=/etc/nut \

Hi, Charles I'm trying compilation but there is no configure command in the cloned git directory of nut. D?a 08.10.2017 o 23:47 Charles Lepple nap?sal(a): > On Oct 8, 2017, at 4:34 PM, tuharsky at misbb.sk wrote: >> 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

[As posted as Ubuntu Question #184284 on Launchpad] Hi, I try to set up nut (2.4.3) on my Lucid (10.04.3 LTS) to make use of my old but very trusty UPS (Best Power Fortress 660 LI). Yes, this UPS is old (about 16 years), but with its third battery pack last week it is as good as new. It runs perfectly well with Windows XP, Vista and even Windows 7. But not so with Ubuntu and nut. After

I'm pretty sure, I've install pkg-config, but I will check it monday after my holliday. This is my test steps: - Shutting down nut-client (upsmon) - Only nut-server (driver + upsd) is running - upsmon.conf have been revert to normal shutdown, no upssched - upsc myups return ups stats then: upsmon -K -DDDDD, here is the output: kill: No such process UPS: myups at

Anybody knows what configure command settings FreeNAS use to compile NUT? More info on my journey: http://forums.freenas.org/index.php?threads/nobreak-bz1200-br-back-ups-rs-1200va-600w-bivolt-115-nt.20247/ Thanks Bruno -------------- next part -------------- An HTML attachment was scrubbed... URL:

I've been wanting to build the trunk since Arjen added the powerpanel driver... been having a little trouble... after running these commands: /usr/local/libexec/automake19/aclocal -I m4 /usr/local/libexec/autoconf259/autoheader /usr/local/libexec/automake19/automake -ac /usr/local/libexec/autoconf259/autoconf ./configure --with-cgi --with-user=nutmon

- 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

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