similar to: NUT & UPS, how to shut down client after 2 min on battery?

Now I have this in /etc/nut/upsmon.conf (my QNAP NAS wants admin and 123456 or not working) RUN_AS_USER root MONITOR qnapups at localhost 1 admin 123456 master MONITOR qnapups at 192.168.222.252 3493 admin 123456 slave MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/killpower NOTIFYFLAG ONLINE SYSLOG+EXEC

Citeren Arnaud Quette <aquette op alioth.debian.org>: > +.SS "Repetitive timeout and staleness" > + > +Some models tends to be unresponsive with the default polling frequency. > +The result is that your system log will have lots of messages like: > +.nf > + usb 2-1: control timeout on ep0in > + usb 2-1: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 128 rq

Gentlemen, I think this question is mainly for Arnaud again: When I run my UPS directly with newhidups -D -D -D, with no data changes, and I then observe the interaction with my UPS (still Back-UPS ES 650 FW:818.w1.D USB FW:w1), I see the updateinfo cycle through 3 different forms: (1) a (2 bytes) => 06 08 notification that provides one item: UPS.PowerSummary.APCStatusFlag Note that

Hello gents, while getting rid of gettimeofday, I've spotted something I'd like to discuss in implementation of socket polling in driver/main.c::main and driver/dstate.c::dstate_poll_fds My observations follow: 1/ I'm not very happy with the poll mechanism design as whole. I mean, typically, you implement the poll as { poll(); process(); }* loop; in pseudo-code: shut_down = false;

On Mon, Jun 18, 2018 at 1:37 PM Richard W.M. Jones <rjones@redhat.com> wrote: > On Thu, Jun 14, 2018 at 09:24:48PM +0300, Nir Soffer wrote: > > On Thu, Jun 14, 2018 at 9:16 PM Nir Soffer <nirsof@gmail.com> wrote: > > > + headers = {"Content-Type": "application/json", > > > + "Content-Length", str(len(buf))} >

> - drivers/dstate-hal.[ch]: added sleep here, to limit the polling rate > (previously, the driver would completely ignore the poll interval and > would run upsdrv_updateinfo() without any delay in between) > > The changes to dstate-hal.[ch] should probably be backported to Testing > ASAP, since ignoring the poll_interval is not a good idea (you'll be > basically polling

Hi - I've told lots of people about the Flash Operator Panel before, but I've never actually used it myself. I've got it all set up nicely, but I can't seem to authenticate to the asterisk manager (which is running on the same box). When I set the op_server.pl to give debug messages, it shows that it can reach the asterisk manager, but cannot authenticate: ** Asterisk

Citeren Arnaud Quette <aquette.dev at gmail.com>: > Author: keyson-guest > Date: Wed Feb 4 15:03:36 2009 > New Revision: 1765 > > Log: > - Added mocrodowell.c/h into drivers/. add man/microdowell.8. Adjusted > drivers/Makefile.am and man/makefile.am. Adjusted the code for 2.4.0 in the > microdowell.c. Besides the things already mentioned by others and the obvious

On Mon, Jun 18, 2018 at 9:23 PM Richard W.M. Jones <rjones@redhat.com> wrote: > On Mon, Jun 18, 2018 at 08:55:13PM +0300, Nir Soffer wrote: > > On Mon, Jun 18, 2018 at 1:37 PM Richard W.M. Jones <rjones@redhat.com> > > wrote: > > > > > On Thu, Jun 14, 2018 at 09:24:48PM +0300, Nir Soffer wrote: > > > > On Thu, Jun 14, 2018 at 9:16 PM Nir

On Mon, Jun 18, 2018 at 08:55:13PM +0300, Nir Soffer wrote: > On Mon, Jun 18, 2018 at 1:37 PM Richard W.M. Jones <rjones@redhat.com> > wrote: > > > On Thu, Jun 14, 2018 at 09:24:48PM +0300, Nir Soffer wrote: > > > On Thu, Jun 14, 2018 at 9:16 PM Nir Soffer <nirsof@gmail.com> wrote: > > > > + headers = {"Content-Type":

This is the patch to include SVN revision level in version number displays. There should be two enclosures; the patch itself and a new source file. common/upsversion.c. upversion.c defines a single function. upsversion(), that returns a version string for display. Some Makefile trickery ensures that this file will be recompiled whenever the project's SVN revision level has changed since it

I'm having problems adding users with usrmgr. I can run the scripts from my smb.conf fine from command line and do what I need to. But, when adding users with usrmgr, the login script and path statements are not identified and I have to go in and edit them manually. Does adding a user with usrmgr not use the add user script from Samba? Or must the user environment variables be added

I think having this logic buried within libhid/libusb (libusb:libusb_open(), line 179 to 206) is ultimately a mistake, albeit one that I am probably responsible for. Would it make sense to confine libhid to low-level operations, and leave the decision of trying to reopen vs. retrying to open to the high-level driver, in this case usbhid-ups? I envision that the code in usbhid-ups:reconnect_ups()

On Thu, Jun 14, 2018 at 09:24:48PM +0300, Nir Soffer wrote: > On Thu, Jun 14, 2018 at 9:16 PM Nir Soffer <nirsof@gmail.com> wrote: > > + headers = {"Content-Type": "application/json", > > + "Content-Length", str(len(buf))} There were a few Python syntax errors such as this one. They can be found by running: make -C v2v check

2011/2/15 Lupe Christoph > On Monday, 2011-02-14 at 21:54:20 -0000, Arnaud Quette wrote: > > I definitely need more info! > > please reply to ALL: > > > - what is the exact model and date of manufacturing? > > SmartUPS 300I NET. I have the serial number (GS9809283199) but no date. > it seems to be a recent model. > - are you sure this unit is ok? > >

2011/2/15 Lupe Christoph > On Monday, 2011-02-14 at 21:54:20 -0000, Arnaud Quette wrote: > > I definitely need more info! > > please reply to ALL: > > > - what is the exact model and date of manufacturing? > > SmartUPS 300I NET. I have the serial number (GS9809283199) but no date. > it seems to be a recent model. > - are you sure this unit is ok? > >

Hello, I'm trying to setup a UPS configuration whereas I have one physical UPS but two UPS entities loaded by the system used by different network slaves. In my ups.conf configuration I have ... [ups] driver = apcsmart port = /dev/ttyS0 desc = "APC UPS" [qnapups] driver = dummy-ups port = ups at localhost desc = "APC UPS for

On Sep 12, 2013, at 7:47 PM, Derek Rachul <drachul at gmail.com> wrote: > I tried reversing the order of the definitions in the config file, and it does seem to change the order in which they're loaded (at least according to the system logs) however the error remains. I don't have any experience using the dummy-ups driver on the same host as the real UPS driver, so this is a

[please keep the list CC'd. Thanks!] On Sep 16, 2013, at 8:11 PM, Derek Rachul <drachul at gmail.com> wrote: > On Mon, Sep 16, 2013 at 4:36 PM, Charles Lepple <clepple at gmail.com> wrote: >> On Sep 12, 2013, at 7:47 PM, Derek Rachul <drachul at gmail.com> wrote: >> >> > I tried reversing the order of the definitions in the config file, and it does

Good day. Can not perform shutdowns Ups. Please help. Details of our installation are: OS: Turris Omnia (TO) NUT version: 2.7.4-5 Installation method: from package UPS device: EATON UPS 5SC 500i , 230V, 350W, 500VA, USB bought in jun 2018 If you connect to TO UPS via USB, the /dev/hidraw0 device will be created. No any programs from NUT package is not running. When I run: /lib/nut/usbhid-ups