similar to: One more try at nut, this time on debian 7.8 (wheezy)

On Feb 18, 2015, at 7:56 PM, Gene Heskett <gheskett at wdtv.com> wrote: > Even though I installed nut-doc, there are no man pages so I am running in > the dark again. They seem to be in the file list: https://packages.debian.org/wheezy/amd64/nut-client/filelist Is $MANPATH set to something strange? > > Where is the initial config and startup procedure to be found? ISTR it

Hi Charles; I had nut working from before, but managed to lock up something and had to reboot. Nut is in the stuff to start at boot time, but is not now capable to being restarted with the nut script in /etc/init.d, claiming it is disabled: gene at coyote:/usr/src/nut-2.7.2/docs/man$ sudo service nut start * nut disabled, please adjust the configuration to your needs * Then set MODE to a

On Tuesday 18 August 2015 09:50:32 Charles Lepple wrote: > On Aug 18, 2015, at 3:27 AM, Gene Heskett <gheskett at wdtv.com> wrote: > > Greetings all; > > > > Is it possible to set a logging option in one of the config files so > > that when we have a 1 second power bump, the date is included, both > > in the log, and in the -wall broadcast? > > Hey

Hi Gene, On Oct 18, 2014, at 7:35 PM, Gene Heskett <gheskett at wdtv.com> wrote: > Greetings; > > I found pdf user manual which explains a few things that might help. > > However, for a ubuntu flavor, the various .conf etc files seem to be in > /etc/nut. We have an open ticket about that[*]; basically, the official NUT documentation needs to be a bit more explicit

Greetings; I found pdf user manual which explains a few things that might help. However, for a ubuntu flavor, the various .conf etc files seem to be in /etc/nut. But this pdf says they are in /usr/local/ups/etc, and yes indeed there are some there, with the .sample files being owned by root, and the rest are user 503, whoever he may be. Are these just a sample storage in case one needs to

On Sunday 19 October 2014 22:03:23 Charles Lepple did opine And Gene did reply: > Hi Gene, > > On Oct 18, 2014, at 7:35 PM, Gene Heskett <gheskett at wdtv.com> wrote: > > Greetings; > > > > I found pdf user manual which explains a few things that might help. > > > > However, for a ubuntu flavor, the various .conf etc files seem to be > > in

Hi Charles; I hope this finds you well. Here is dmesg output: gene at coyote:~$ dmesg |grep Belkin [ 3.315667] usb 2-3: Product: Belkin UPS [ 3.315669] usb 2-3: Manufacturer: Belkin [ 4.084258] generic-usb 0003:050D:0751.0009: hiddev0,hidraw4: USB HID v1.11 Device [Belkin Belkin UPS] on usb-0000:00:02.0-3/input I have configured it to use this generic-usb, and probably made it less

On Tuesday 14 October 2014 08:19:02 Charles Lepple did opine And Gene did reply: > usbhid-ups Added that, but only get this at "sudo service nut start" gene at coyote:/etc/init.d$ sudo service nut start * Starting Network UPS Tools [ OK ]

On Sun, Mar 1, 2015 at 2:23 PM, Gene Heskett <gheskett at wdtv.com> wrote: > Hi Charles; I hope this finds you well. Hi Gene, > Here is dmesg output: > gene at coyote:~$ dmesg |grep Belkin > [ 3.315667] usb 2-3: Product: Belkin UPS > [ 3.315669] usb 2-3: Manufacturer: Belkin > [ 4.084258] generic-usb 0003:050D:0751.0009: hiddev0,hidraw4: USB HID v1.11 Device

On Dec 1, 2014, at 9:43 AM, Gene Heskett <gheskett at wdtv.com> wrote: > FWIW, before I asked, I redid the nut ./configure --with-doc=auto, then a > make. Then I step into the docs directory and do a sudo make install, > which it appears to do. But no manpages were install despite the command > line echo showing that they were when I did the sudo make install, but I >

On Dec 1, 2014, at 9:43 AM, Gene Heskett <gheskett at wdtv.com> wrote: > Hi Charles; > > I had nut working from before, but managed to lock up something and had to > reboot. Nut is in the stuff to start at boot time, but is not now capable > to being restarted with the nut script in /etc/init.d, claiming it is > disabled: > > gene at

Greetings Charles; I hope you had a nice Christmas, and will have a happy and prosperous new year in 2016. You mentioned upsrw in a message earlier, so I ran it, and found the shutdown timeout was only 20 seconds. gene at coyote:~$ upsrw myups [input.transfer.high] High voltage transfer point (V) Type: STRING Value: 140 [input.transfer.low] Low voltage transfer point (V) Type: STRING Value:

Greetings Charles; Following the chapter 6, configuration notes, and having configured everything I had done previously in the repo built /etc/nut directory without any success previously, I found when trying: /usr/local/ups/upsdvrctl start, It reported it couldn't open /usr/local/ups/etc/ups.conf So I copied what I had done before to that path by mv'ing them with mc. Then I checked

Greetings; Its unk because whats plugged in seems to be blocking the rear name plate. About all I can recall is that its big, 3 battery unit, rated somewhere north ob 1250 VA. Its an 050D:0751 Belkin. What driver should I use, and what file is that set in? The nut version presently and freshly installed is from the Ubuntu 10.04.4 LTS repo's. Probably old, but IIRC it also worked with

Greetings all; Is it possible to set a logging option in one of the config files so that when we have a 1 second power bump, the date is included, both in the log, and in the -wall broadcast? We apparently have a substation regulator in the process of failing, and the recycle isn't normally slow enough to reset the clocks, but it killing one of my computers w/o actually causing a reboot.

Greetings all; Back to a thread I started back in May of 2008 I think. I never did get this belkin and nut to talking, so I thought I'd make another run at it. Trying to run the driver as the user gene, I'm getting this: --------------------------- [root at coyote ups]# su gene -c "/sbin/belkin -D -a myups" Network UPS Tools - Belkin Smart protocol driver 0.21 (2.2.2) debug

Hi Charles; I think its not working yet even though I seem to be getting only one error, but I cannot seem to get upsmon to output the current ups status. So, since I cannot find any manpages (is that a separate package, if so I did not see it in the repo.) about the only error I can get out of it is that it is not listening on localhost:3493. Yet that is specified in the conf files: ene

On Sunday 12 May 2019 03:10:13 pm Charles Lepple wrote: > On May 12, 2019, at 2:51 PM, Gene Heskett wrote: > > On Sunday 12 May 2019 02:41:02 pm Charles Lepple wrote: > >> /lib/nut/usbhid-ups -a myups -DD > > > > gene at coyote:~$ /lib/nut/usbhid-ups -a myups -DD > > Network UPS Tools - Generic HID driver 0.41 (2.7.4) > > USB communication driver 0.33

On Thursday, February 19, 2015 10:16:41 PM Charles Lepple wrote: > On Feb 19, 2015, at 8:55 AM, Gene Heskett <gheskett at wdtv.com> wrote: > > On Wednesday, February 18, 2015 08:11:13 PM Charles Lepple wrote: > > [...] > > > >> On recent Debian and Ubuntu with 2.7.2 and > >> earlier, there was an issue where the udev rules file needed to be >

On Tuesday 07 May 2019 09:49:47 am Charles Lepple wrote: > On May 7, 2019, at 9:09 AM, Gene Heskett wrote: > > On Tuesday 07 May 2019 08:38:44 am Charles Lepple wrote: > >> On May 7, 2019, at 5:06 AM, Gene Heskett wrote: > >>> New testing install(stretch) > >>> pulled in nut stuff from repo. > >>> copied old wheezy configs to /etc/nut,