similar to: got nut 2.8.1 but despite reinstall, shows 2.7.4

On 5/22/23 03:10, gene heskett wrote: > Which file in the nut I pulled a month ago, should I start with to get > the new version actually running? I still get - -V=2.7.4 The UPGRADING file tsalks about a 2.8.1, but I have started with the autogen 3 times in the usual sequence, winding up with 2.7.4 twice, and while the third time is supposed yo be a charm, now it won't run at all.

I think you have just the libraries - also you'd need a *-dev package for headers. The docs/config-prereqs.txt has the dependencies in more detail. In quick practice, --with-all=auto can help better if you don't monitor a netxml device ;) HTH Jim On Mon, May 22, 2023, 15:24 gene heskett <gheskett at shentel.net> wrote: > On 5/22/23 03:10, gene heskett wrote: > > Which

gene heskett <gheskett at shentel.net> writes: > Which file in the nut I pulled a month ago, should I start with to get > the new version actually running? I still get - -V=2.7.4 It is likely that you have built new nut but old nut is still on your system. I do a 'sudo make install' to write over the distribution nut (on NetBSD/pkgsrc, surely not what you are using).

On 5/22/23 07:13, Greg Troxel wrote: > gene heskett <gheskett at shentel.net> writes: > >> Which file in the nut I pulled a month ago, should I start with to get >> the new version actually running? I still get - -V=2.7.4 > > It is likely that you have built new nut but old nut is still on your > system. I do a 'sudo make install' to write over the

>>gene heskett <gheskett at shentel.net> writes: >>>Which file in the nut I pulled a month ago, should I start with to get >>>the new version actually running? I still get - -V=2.7.4 >On 5/22/23 07:13, Greg Troxel wrote: >>It is likely that you have built new nut but old nut is still on your >>system. I do a 'sudo make install' to write over

On Mon, 2023-05-22 at 15:54:51 +0200, Matus UHLAR - fantomas wrote: > > > gene heskett <gheskett at shentel.net> writes: > > > > Which file in the nut I pulled a month ago, should I start with to get > > > > the new version actually running? I still get - -V=2.7.4 > > > On 5/22/23 07:13, Greg Troxel wrote: > > > It is likely that you have

On Monday 22 June 2020 09:50:50 Larry Fahnoe wrote: > On Mon, Jun 22, 2020 at 8:27 AM Gene Heskett <gheskett at shentel.net> wrote: > > > On Jun 22, 2020, at 8:52 AM, Gene Heskett wrote: > > > > pi at rpi4:~ $ upscmd myups *test.battery.start.quick* > > > > Username (pi): > > > > Password: > > > > Unexpected response from upsd:

On Monday 22 June 2020 09:18:29 Charles Lepple wrote: > On Jun 22, 2020, at 8:52 AM, Gene Heskett wrote: > > pi at rpi4:~ $ upscmd myups test.battery.start.quick > > Username (pi): > > Password: > > Unexpected response from upsd: ERR ACCESS-DENIED > > > > Looking at /etc/nut/uspd.users, I (me, pi) should be able to do > > that. ??? > > Hi Gene,

Greetings all; Does nut build on an r-pi4b? I have an r-pi4b running one of my cnc machines and the power bump performance due to the size of its psu and the fairly rapid start time of my standby generator, does not allow a full powerdown restart to take place, leaving the pi in a crashed state. I've purchased a factory refurbed cyberpower ups rated at 650 WA which I intend to figure

On Monday 22 June 2020 15:26:23 Larry Fahnoe wrote: > On Mon, Jun 22, 2020 at 12:26 PM Gene Heskett <gheskett at shentel.net> wrote: > > So I just edited /etc/nut/upsd.users to add both the commands it > > claims to have but get this response to either: > > > > pi at rpi4:~ $ upscmd myups test.battery.start.quick > > Username (pi): pi > > Password:

On Wednesday 08 January 2020 09:37:10 Roger Price wrote: > On Tue, 7 Jan 2020, Gene Heskett wrote: > > ● nut-monitor.service - Network UPS Tools - power device monitor and > > shutdown controller > > Loaded: loaded (/lib/systemd/system/nut-monitor.service; enabled; > > vendor preset: enabled) > > Active: failed (Result: protocol) since Tue 2020-01-07 07:19:19

On Sunday 12 January 2020 11:14:13 Charles Lepple wrote: > On Jan 12, 2020, at 9:56 AM, Gene Heskett wrote: > >> Instant return, logging this: > > > > in /tmp/info > > > >> 0.000000 Error: too many non-option arguments. Try -h for > >> help. Network UPS Tools - Generic HID driver 0.41 (2.7.4) > >> USB communication driver 0.33 >

On Jun 22, 2020, at 3:36 PM, Charles Lepple wrote: > > On Jun 22, 2020, at 1:26 PM, Gene Heskett wrote: >> >> So I just edited /etc/nut/upsd.users to add both the commands it claims >> to have but get this response to either: > > In your original example, you had multiple “instcmd =“ lines for one user- I think the allowed commands all need to be listed on one

On Sep 5, 2020, at 5:23 AM, Roger Price wrote: > > On Sat, 5 Sep 2020, Gene Heskett wrote: > >> But runs normally if started. On a rpi4 running an uptodate raspbian buster, how do I set it to auto start at boot time? > > Hello Gene, By "auto start" I assume you mean the automatic power on of a box when wall power returns after a power failure. For this to work,

But runs normally if started. On a rpi4 running an uptodate raspbian buster, how do I set it to auto start at boot time? Thanks. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D.

On Monday 22 June 2020 08:19:15 Charles Lepple wrote: > > On Jun 18, 2020, at 12:39 PM, Mike Dillinger wrote: > > > > ups.test.result: No test initiated > > I’d recommend a battery test. Starting the test via the front panel > should be sufficient, or you might be able to do it with upscmd. from man pi at rpi4:~ $ upscmd -l myups Instant commands supported on UPS

On Monday 26 October 2020 09:01:31 Charles Lepple wrote: > On Oct 25, 2020, at 11:52 AM, Robert Stocker <kneadtoknow at gmail.com> wrote: > > Init SSL without certificate database > > battery.charge: 100 > > battery.charge.low: 10 > > battery.charge.warning: 20 > > battery.mfr.date: CPS > > battery.runtime: 15690 > > battery.runtime.low: 300

On Monday 22 June 2020 18:50:25 Gene Heskett wrote: > On Monday 22 June 2020 18:03:16 Charles Lepple wrote: > > On Jun 22, 2020, at 3:36 PM, Charles Lepple wrote: > > > On Jun 22, 2020, at 1:26 PM, Gene Heskett wrote: > > >> So I just edited /etc/nut/upsd.users to add both the commands it > > >> claims to have but get this response to either: > >

On Jan 9, 2020, at 5:51 PM, Gene Heskett wrote: > > On Thursday 09 January 2020 16:59:12 Charles Lepple wrote: > >> On Jan 9, 2020, at 4:39 PM, Gene Heskett <gheskett at shentel.net> wrote: >>> So for starters, what's the best ./configure command line? >> >> There’s this page for matching the layout of an existing Debian >> install: >>

On 2020-09-05 05:23, Roger Price wrote: > On Sat, 5 Sep 2020, Gene Heskett wrote: > >> But runs normally if started. On a rpi4 running an uptodate raspbian >> buster, how do I set it to auto start at boot time? > > Hello Gene, By "auto start" I assume you mean the automatic power on of a box > when wall power returns after a power failure. For this to