Re: [Nut-upsdev] [networkupstools/nut] Improve upssched example in documentation (#293) (fwd)

Arnaud Quette writes: moving to 2.7.6 to ease 2.7.5 release, while waiting for feedback Issue 293 https://github.com/networkupstools/nut/issues/293 is due to my misunderstanding of the upssched timers. I wrongly assumed that they were files. I now understand that

Re: [Nut-upsdev] Clarification to man upssched.conf

On Tue, 11 Jul 2017, Jim Klimov wrote: On July 5, 2017 9:55:13 AM GMT+02:00, Roger Price <ro...@rogerprice.org> wrote: I propose adding the sentence "If more than one AT matches the notifytype and upsname, the AT declarations are executed in the order in which they appear in up

[Nut-upsdev] Clarification to man upssched.conf

I would like to add a sentence to the man page for upssched.conf. After the sentence "Note that any AT that matches both the notifytype and the upsname for the current event will be used." I propose adding the sentence "If more than one AT matches the notifytype and upsname, the AT

Re: [Nut-upsdev] Proposed new documentation "Configuration Examples"

On Wed, 21 Jun 2017, Jim Klimov wrote: On June 21, 2017 5:26:47 PM GMT+02:00, Tim Dawson wrote: My thought of #2 require none of that . . . I have a server with two supplies, and two UPS units. One supply is on each UPS, and clients are distributed otherwise to balance.

Re: [Nut-upsdev] Proposed new documentation "Configuration Examples"

On Wed, 21 Jun 2017, Jim Klimov wrote: Regarding systemd, there are many valid paths, applied in order of preference (rising from distro to system-local). It may be worded better in official docs, but in short, the /usr/lib/systemd and to an extent /lib/systemd trees can be considered

Re: [Nut-upsdev] Proposed new documentation "Configuration Examples"

On Tue, 13 Jun 2017, Tim Dawson wrote: Allow me to suggest a couple more sample configs: 1) Server as UPS controller with clients that are also on UPS, considering shutdown sequencing and It would be good to add this, but I lack the depth of understanding needed to write a tutorial. For

Re: [Nut-upsdev] Proposed new documentation "Configuration Examples"

On Tue, 13 Jun 2017, Charles Lepple wrote: On Jun 9, 2017, at 10:16 AM, Roger Price wrote: To address this, I propose a "NUT configuration for Noobs" which is called "Configuration Examples". I am also curious whether you tried to edit any of the existing NUT documenta

[Nut-upsdev] Proposed new documentation "Configuration Examples"

Most of the questions asked in the nut-user mailing list seem to me to be either erudite technical discussion of new and exotic UPS units, or n00b questions of the style "I have this old UPS so I installed NUT but it didn't work". NUT is thoroughly documented with man pages and User Manual,

[Nut-upsdev] Allow status name as alternative

Alongside the discussion of ALARM handling in upsmon, https://github.com/networkupstools/nut/issues/415 , I would like to suggest a minor change in upsmon which would help the documentation explain the flow of statuses in NUT. Certain values in upsmon.conf correspond to statuses. I propose

[Nut-upsdev] 2.7.4 make install fails: libnutclient.so.0.0.0 missing

I upgraded an operating system to openSUSE 42.2, kernel 4.4 and recompiled nut 2.7.4. ./configure, make clean and make went well, but make install failed. Make reports Making install in clients make[1]: Entering directory '/mnt/home/rprice/nut/nut-2.7.4.dev/clients' make[2]: Entering

Re: [Nut-upsdev] CyberPower SX650G no driver.

On Sun, 30 Oct 2016, Raymond Day wrote: Below you'll find one or more lines starting with 'exec:' followed by an absolute path to the driver binary and some command line option. This is what the driver starts and you need to copy and paste that line and append the debug flags to that line

Re: [Nut-upsdev] Proposal for technique to stop a timer at any moment

Here is patch 2 of 2. Roger diff -rup -x '*.html' -x '*.8' -x '*.5' nut-2.7.4.orig/docs/man/upsd.txt nut-2.7.4.dev/docs/man/upsd.txt --- nut-2.7.4.orig/docs/man/upsd.txt2015-12-29 09:42:34.0 +0100 +++ nut-2.7.4.dev/docs/man/upsd.txt 2016-07-07 10:08:51.939354892 +0200 @@ -119,6

Re: [Nut-upsdev] Proposal for technique to stop a timer at any moment

Here is patch 1 of 2. Roger diff -rup nut-2.7.4.orig/clients/upsmon.c nut-2.7.4.dev/clients/upsmon.c --- nut-2.7.4.orig/clients/upsmon.c 2015-12-29 13:08:34.0 +0100 +++ nut-2.7.4.dev/clients/upsmon.c 2016-07-01 09:46:21.567766415 +0200 @@ -525,6 +525,18 @@ static int

[Nut-upsdev] Proposal for technique to stop a timer at any moment

Dear list, I would like to propose a set of patches which make it possible for a upssched-cmd script to stop a timer at an arbitrary moment. If you find this of interest, I will submit a set of patches to 2.7.4. Roger Introduction The comments at the top of upssched.c say << *

[Nut-upsdev] ./configure excludes USB drivers and documentation

Sorry for such a noob question, but I'm having a problem with 2.7.4 ./configure . I down loaded the 2.7.4 tarball, unzipped. read the INSTALL and typed ./configure . The output of ./configure shows "build serial drivers: yes" and build everything else is "no". Looking at config.log, I see