similar to: Nut-upsuser Digest, Vol 147, Issue 2

By side effect, lack of "killpower" touch file works to not-tell the OS shutdown integration on OMV to turn off the UPS. A more proper way about this is generally to change MONITOR back-ups 1 monmaster 4L[p9<0Vi|Z>xKgK master (see my earlier message or docs about primary/master vs. secondary/slave clients), to MONITOR back-ups 1 monmaster 4L[p9<0Vi|Z>xKgK slave and it

Roger, here is my output of ps -elf |grep upssched root at nutpi:~# ps -elf |grep upssched 0 S root 1242 1191 0 80 0 - 1834 pipe_w 05:23 pts/0 00:00:00 grep upssched No timer, just the grep of upssched.. On Mon, Jan 27, 2020 at 4:27 AM <nut-upsuser-request at alioth-lists.debian.net> wrote: > Send Nut-upsuser mailing list submissions to >

As fast as I know, the standard NUT package will not command your power supply off unless customizations are made. Devices like Synology have an option to command the UPS off. What is acting as your NUT server? Your server PC? On Fri, Sep 6, 2024, 11:10 AM <nut-upsuser-request at alioth-lists.debian.net> wrote: > Send Nut-upsuser mailing list submissions to > nut-upsuser at

I am also having Windows Issues, Refer back to the post I received from Charles Lepple. He gave me the details on how to resolve the missing USB driver issue - Although I would be very interested in what you find as I have not found time to revisit the issue yet.. ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 19 Jul 2016 17:28:51

> The directory /etc/nut created at .deb install time is > O755 root:nut Could be. Then I guess I did the "chmod 660" for the folder + its files at once. > although 750 is also fine, but might > prevent some access to non secured files Yeah, made it 751 since, so I can use the cgi status script. That's as fancy as it gets in my setup ;) Well, unless it turns out the

> Today's Topics: > > 1. Re: Possible support for Trust 1300VA LCD Management UPS? > (Charles Lepple) > Hmm, you have both libusb-compat and libusb-legacy. Unfortunately, > that alone doesn't tell us what NUT is linked against. > > What does "otool -L <path-to-drivers>/blazer_usb" show? Not sure what > that path would be for MacPorts, but

Hello Gene, > I just had a similar situation using heyu on /dev/ttyUSB0. I could > find the udev rule that had changed it, so I took the next best > route, got root and put a chmod and a chown of that port in my > /etc/rc.local file, which runs last at bootup. And heyu is once > again a happy camper. > > This might not be your problem, but its something to check. thank for

?Hello Sabine, this seems as a problem with PATH env. variable; if you issue the command by hand, you do so in an environment with PATH set so that the binaries are found. I guess that the nut user doesn't have so nice PATH, being non-interactive. Try to add full paths to your binaries in the command and see what happens... Regards, vasek -- Vaclav Krpec NUT developer

> Lots of good progress here! I tried to enable a few more commands for > your model. For instance, the "M" values seem to be min/max voltage, > so there is a "reset.input.minmax" command to use with upscmd. Also, > you can trigger a battery test with "test.battery.start". I assume the > work the same way as on Protocol 3003 :-) > > The attached

---> On 15/03/2009 8:00 AM, nut-upsuser-request at lists.alioth.debian.org wrote: > Message: 1 > Date: Sat, 14 Mar 2009 21:47:08 +0100 > From: Arjen de Korte <nut+users at de-korte.org> > Subject: Re: [Nut-upsuser] Weird Load and Battery Temp Readings > To: nut-upsuser at lists.alioth.debian.org > Message-ID: <20090314214708.37122w00w79l6u9s at mail.de-korte.org>

On Tuesday 10 June 2008 08:00:39 am nut-upsuser-request at lists.alioth.debian.org wrote: > Message: 2 > Date: Tue, 10 Jun 2008 10:58:11 +0200 (CEST) > From: "Arjen de Korte" <nut+users at de-korte.org> > Subject: Re: [Nut-upsuser] Nut-upsuser Digest, Vol 36, Issue 5 > To: "Alex Peyser" <a.peyser at umiami.edu> > Cc: nut-upsuser at

Le 23/06/2011 14:00, nut-upsuser-request at lists.alioth.debian.org a ?crit : > Send Nut-upsuser mailing list submissions to > nut-upsuser at lists.alioth.debian.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser > or, via email, send a message with subject or body 'help' to >

Hello, I will thank you all for your support about my network problem on NUT Not it is solved and I will thank you a lot ! Best regards Thierry Le sam. 31 août 2019 à 07:00, <nut-upsuser-request at alioth-lists.debian.net> a écrit : > Send Nut-upsuser mailing list submissions to > nut-upsuser at alioth-lists.debian.net > > To subscribe or unsubscribe via the World

It is possible at least on linux to get the port associated with a device from userspace - I'd assume that on each platform it's possible, just that libusb is incomplete (on top of being undocumented). Here's a patch for matching portnum on linux, with a few pieces pulled from libusb. It lacks autoconf macros to isolate it -- but it does appear to work. Regards, Alex Peyser On

THANKS, but the 'megatec' driver only works whith windows OS via USB, and i need it for red hat OS with USB-serial connection... Please, anybody can help me.... nut-upsuser-request@lists.alioth.debian.org escribi?: Send Nut-upsuser mailing list submissions to nut-upsuser@lists.alioth.debian.org To subscribe or unsubscribe via the World Wide Web, visit

Hi Vladimir, I have got 2.0.3 working on netBSD 3.0. To get it operational I needed to do the following (most of this is from memory...). 1). Recompile kernel with uhid removed. If uhid ataches to the device then libusb is not able to. Have to allow generic usb driver ugen to claim port. >From dmesg usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: VIA Technologies UHCI root hub, class

This is the first time that i had to use E-mail like forums i'm only hitting reply to mail NOT replay to all mails THIS IS upssched.conf # This file is auto-generated by openmediavault (https://www.openmediavault.org) # WARNING: Do not edit this file, your changes will get lost. CMDSCRIPT /usr/bin/upssched-cmd PIPEFN /run/nut/upssched.pipe LOCKFN /run/nut/upssched.lock AT COMMOK * EXECUTE

THIS IS systemctl list-units | grep UPS nut-driver at back-ups.service

Hi, Thanks for help. - I download the last version of NUT, 2.7.2.6 - I install library: nss-devel gcc-c++ So now I didn't get last errors on make. But I get a new one when I try to do - make install --------------------------- *[root at artesano nut-2.7.2.6]# make install* Making install in include make[1]: Entering directory `/home/artesano/Downloads/nut-2.7.2.6/include'

Here are my permissions and user info. Let me know if there is anything else I should check pi at nutpi:~ $ ls -alt /etc/nut total 56 drwxr-xr-x 87 root root 4096 Jan 26 15:22 .. drwxr-xr-x 2 root nut 4096 Jan 26 13:53 . -rw-r----- 1 root nut 4719 Jan 26 13:15 upssched.conf -rw-r----- 1 root nut 15347 Jan 26 11:25 upsmon.conf -rw-r----- 1 root nut 1543 Jan 26 10:02 nut.conf -rw-r-----