search for: ar01s07

...e to find that my script had myriad issues when run under the nut user. All remedied now. As I progress, I may well end up migrating to the upssched. As a newbie I was simply following the documented "simple" way described here <https://networkupstools.org/docs/user-manual.chunked/ar01s07.html>. Thanks to all! On 7/18/2019 3:38 PM, Roger Price wrote: > On Thu, 18 Jul 2019, David White wrote: > >> NOTIFYCMD? /home/android/nutShutdown.sh >> NOTIFYMSG? ONBATT? "USP %s on battery" >> NOTIFYFLAG? ONBATT? EXEC > > Perhaps before plunging into u...

Per: http://soft-switch.org/spandsp_faq/ar01s07.html FAXing with spandsp keeps giving me core dumps. Its crap, isn't it? Actually the crap in this case is probably libtiff. Versions 3.5.7 and 3.6.0 seem reliable. The FAX image handling in version 3.6.1 is broken. All the core dump problems I have investigated turned out to be due to a v...

...t the timers are only stored in memory. See > checktimers(): > https://github.com/networkupstools/nut/blob/master/clients/upssched.c#L129 Hello Charles, thanks for the link. If timers are only stored in memory then the example given at http://networkupstools.org/docs/user-manual.chunked/ar01s07.html chapter 7.2 is wrong. It is not possible to turn off a timer with rm as shown in #! /bin/sh case $1 in ... ups-back-on-power) /bin/rm -f /some/path/ups-on-battery ;; ......

...down routine directly from the CMDSCRIPT, since there?s no synchronization with the slave systems hooked to the same UPS. FSD is the master?s way of saying "we?re shutting down now like it or not, so you?d better get ready". >> http://networkupstools.org/docs/user-manual.chunked/ar01s07.html If you want to shutdown your slave systems siom, iogate and br from the CMDSCRIPT, you will need to reproduce the NUT protocol of "slaves first", then the master. Your current protocol does not check that the slaves are indeed shutting down. Roger

...ctive over the past year... that said, here are base answers to your questions: 1. there have been recent updates from Alf H?gemark, along with some others. We are currently working hard to release 2.7.1, which will ship these improvements. 2. http://www.networkupstools.org/docs/user-manual.chunked/ar01s07.html cheers, Arno -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20131118/f5d64492/attachment.html>

On Jan 21, 2014, at 9:27 AM, Rafal Oleszek wrote: > So it's impossible to configure upssched to start timer only if all ups > are in status: OB or LB ? Not impossible, just not possible inside a single configuration file. You can always put that logic into an external script called by upssched. -- Charles Lepple clepple at gmail

> On Jan 21, 2014, at 9:27 AM, Rafal Oleszek wrote: > >> So it's impossible to configure upssched to start timer only if all ups >> are in status: OB or LB ? > Not impossible, just not possible inside a single configuration file. You can always put that logic into an external script called by upssched. > Thank for your help Charles. I checked it and it works like you

...mory. See >> checktimers(): https://github.com/networkupst >> ools/nut/blob/master/clients/upssched.c#L129 >> > > Hello Charles, thanks for the link. If timers are only stored in memory > then the example given at http://networkupstools.org/doc > s/user-manual.chunked/ar01s07.html chapter 7.2 is wrong. It is not > possible to turn off a timer with rm as shown in > > #! /bin/sh > case $1 in > ... > ups-back-on-power) > /bin/rm -f /some/path/ups-on-battery >...

On Fri, Jul 19, 2019 at 7:37 PM David White <whitedavidp at yahoo.com> wrote: > As a newbie > I was simply following the documented "simple" way described here > <https://networkupstools.org/docs/user-manual.chunked/ar01s07.html> In addition to the NUT documentation above, you may also profit from the excellent work Roger Price has put into documenting many NUT configuration examples: http://rogerprice.org/NUT/ --Larry -- Larry Fahnoe, Fahnoe Technology Consulting, fahnoe at FahnoeTech.com Minneapol...

I'm developing a new plugin, based on switcher. I have a window created with XCreateWindow. Can I put a window totally on top, even over panels? These are my atoms: state[nState++] = s->display->winStateAboveAtom; state[nState++] = s->display->winStateStickyAtom; state[nState++] = s->display->winStateSkipTaskbarAtom; state[nState++] =

...ectly >from the CMDSCRIPT, since there?s no synchronization with the slave >systems hooked to the same UPS. FSD is the master?s way of saying "we?re >shutting down now like it or not, so you?d better get ready". >> >http://networkupstools.org/docs/user-manual.chunked/ar01s07.html It is not good to shutdown from CMDSCRIPT the master itself. Is it correct? > >If you want to shutdown your slave systems siom, iogate and br from the >CMDSCRIPT, you will need to of "slaves first", >then the master. Your current protocol does not check that the slav...

...irectory created when unzipping nut-2.7.4.tar.gz . Documentation ------------- I propose submitting the documentation changes as plain text editorial comments. The NUT User Manual Chapter 7.2. "The advanced approach, using upssched" http://networkupstools.org/docs/user-manual.chunked/ar01s07.html#_the_advanced_approach_using_upssched is the subject of issue 293 "Improve upssched example in documentation". I propose an example showing how to monitor an unreliable UPS. https://github.com/networkupstools/nut/issues/293 Debugging --------- I find it convenient to be able to t...

Hi, I'm trying to get a better understanding of what a timer is, so I added the following line to upssched.conf # Debug - turn on long-running timer to find out where upssched puts it AT ONBATT * START-TIMER where-am-I 1000 I can then start this timer by pulling the power cord from the wall for just a few seconds. I now have 1000 seconds to find the timer. I don't see it in

Hi ?? I need to shutdown a number of hosts which has not NUT from one which has it. ?? I tried to do it from upssched script (after upssched's timer) like this: case $1 in ??????? earlyshutdown) ??????????????? logger -t upssched-cmd "Early shutdown is started" ??????????????? /bin/sh /usr/local/sbin/shutdown-all-hosts.sh ??????????????? /usr/local/sbin/upsmon -c fsd

Hi all, sorry for this message, but maybe I am the most dumb user in here, so, please accept my appologies asking novice questions. I have tried 6 searched for more than 4 hours now, read all html-man files I could think need to be read and also the major one, but I did not manage to get the NUT to successfully run on my Vista machine. (it runs, but I cannot use it ... see later). I am

hello, I installed with NUT UPS MGE Pulsar Evolution 2200 all orders of arrest, interrogation etc etc ... UPS work well However, I have a problem with the order in NOTIFYCMD upsmon.conf that not run ... I created a script that generates a simply log I indicated in upsmon.conf NOTIFYCMD / home / nut / alert_ups.sh below my upsmon.conf RUN_AS_USER nut MONITOR pulsar at localhost 1 admin1

Hello, I set up a FreeBSD 8.2 system with nut 2.6.1 and a Powerware 5115 connected by RS-232. I expected this setup to shut down before running out of battery power, but I either missed some important configuration or something else went wrong: The syslog says: Jan 9 05:03:42 b1 upsmon[67752]: UPS upsb1 at localhost on battery Jan 9 05:04:42 b1 upsmon[67752]: UPS upsb1 at localhost on line

An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20120104/34be491b/attachment.html>