search for: upsname

...he existing > > clients. When changing the "port" argument to a string, the API should > > also define whether this is allocated (and must be freed) or not. This reminds me: when I was working on branches/upsc_list, the upscli_splitname() function has this comment: /* split [upsname@]hostname[:port] into separate components */ To me, this implies that "upsname@" is optional, but I think this is left over from an older version of NUT (since you have to specify an upsname for upsc). I was thinking that listing all available upsnames would be done like this: "ups...

...Modified: trunk/clients/upsclient.c > ============================================================================== > --- trunk/clients/upsclient.c (original) > +++ trunk/clients/upsclient.c Thu Jan 18 22:07:08 2007 > @@ -912,60 +912,99 @@ > return 0; > } > > -/* split upsname@hostname[:port] into separate components */ > +/* split upsname[@hostname[:port]] into separate components */ > int upscli_splitname(const char *buf, char **upsname, char **hostname, int *port) > { > - char tmp[SMALLBUF], *s; > + char *s, tmp[SMALLBUF]; > > /* paranoia */...

...n exit of the counterpart. 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT command the 'heartbeat at localhost' we were launched to process? 0.000034 [D1] parse_at: 'heartbeat at localhost' in AT command matched the 'heartbeat at localhost' UPSNAME we were launched to process 0.000041 [D1] parse_at: processing CANCEL-TIMER 0.000054 [D2] parse_at: is 'heartbeat at localhost' in AT command the 'heartbeat at localhost' we were launched to process? 0.000057 [D1] parse_at: 'heartbeat at localhost' in AT...

...n exit of the counterpart. 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT command the 'heartbeat at localhost' we were launched to process? 0.000034 [D1] parse_at: 'heartbeat at localhost' in AT command matched the 'heartbeat at localhost' UPSNAME we were launched to process 0.000041 [D1] parse_at: processing CANCEL-TIMER 0.000054 [D2] parse_at: is 'heartbeat at localhost' in AT command the 'heartbeat at localhost' we were launched to process? 0.000057 [D1] parse_at: 'heartbeat at localhost' in AT...

...s, but the exact procedure will depend on the driver you are using (apcsmart or usbhid-ups). Kevin, to collect the command outputs, you will need to either be logged into pfSense (ssh) or use the command prompt in the GUI (Diagnostics / Command Prompt). The command he is asking you to run is “upsc UPSNAME” where UPSNAME is the name you gave the UPS in the GUI. The others would be “upsrw UPSNAME” and “upscmd -l UPSNAME”. To get the relevant system logs, you would execute "clog /var/log/system.log | grep -i ups”. Denny

Hi everybody, i'm trying to use the UPSNAME environment variable within the script launched by upssched, and although it is correctly written and thus read by my script, it doesn't get updated when multiple UPSes are configured. To be more precise i'm monitoring 2 UPSes and using AT *EVENT* * *OPERATION* *handle *to manage events i...

...e release of nut-2.0.5 it was possible to have a working configuration without configuring anything in 'ups.conf'. Since then, this no longer works, as the server will only look for driver sockets for UPSes that have been configured in 'ups.conf' (since the socket is named after the UPSname). Drivers will use the old naming scheme '<driver>-<port>' if the UPSname can't be found in 'ups.conf'. From time to time, people are confused by this, especially since this used to work up to (and including) nut-2.0.4. Some distributions even offered this as the st...

...7.4.dev/clients/upsmon.c 2016-07-01 09:46:21.567766415 +0200 @@ -525,6 +525,18 @@ static int get_var(utype_t *ups, const c numq = 2; } + /* Subcommands for polling SIGUSR1, SIGUSR2 RP */ + if (strcmp(var, "SIGUSR1") == 0) { + query[0] = "SIGUSR1"; + query[1] = ups->upsname; + numq = 2; + } + if (strcmp(var, "SIGUSR2") == 0) { + query[0] = "SIGUSR2"; + query[1] = ups->upsname; + numq = 2; + } + if (!strcmp(var, "status")) { query[0] = "VAR"; query[1] = ups->upsname; @@ -1518,7 +1530,25 @@ static void pollups...

...Inc. CP1500 AVR UPS I am guessing that 'ls -l /dev/bus/usb/004/002' shows that the device node is not owned by the NUT gid? > Why doesn't > "upsdrvctl start" allow nut to find the UPS when it can find it without a > problem with the options "-u root start <upsname>"? The NUT USB drivers use libusb, which need read/write access to the /dev node for the UPS. The "-u root" hack tells the driver not to drop privileges from root to the 'nut' system user. > Second why doesn't nut create the .pid files and the usbhid file with roo...

...rsion trunk). For more info on getting and compiling the development release: http://buildbot.ghz.cc/~buildbot/docs/r2003-144/website/download.html Note that you don't need to install nut ; simply running from the build directory is sufficient, using: $ sudo ./drivers/megatec_usb -DDDDD -a <upsname> you might also give a try to blazer_usb, which will replace megatec* $ sudo /lib/nut/blazer_usb -DDDDD -a <upsname> and/or $ sudo ./drivers/blazer_usb -DDDDD -a <upsname> cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) P...

...(*) I managed to reproduce the problem with current NUT master and an adapted copy of your posted configs and script :D Experimental debugging now sounds possible. (*) PC under the desk wails with all its cooling fans as soon as I started the client which spawned a daemon and itself had exited: $ UPSNAME=heartbeat at localhost NOTIFYTYPE=ONBATT NUT_STATEPATH=/dev/shm NUT_CONFPATH=`pwd`/tests/NIT/tmp/etc ./clients/upssched -DDDDDDDD 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT command the 'heartbeat at localhost' we were launched to process? 0.000053 [D1] p...

...(*) I managed to reproduce the problem with current NUT master and an adapted copy of your posted configs and script :D Experimental debugging now sounds possible. (*) PC under the desk wails with all its cooling fans as soon as I started the client which spawned a daemon and itself had exited: $ UPSNAME=heartbeat at localhost NOTIFYTYPE=ONBATT NUT_STATEPATH=/dev/shm NUT_CONFPATH=`pwd`/tests/NIT/tmp/etc ./clients/upssched -DDDDDDDD 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT command the 'heartbeat at localhost' we were launched to process? 0.000053 [D1] p...

...an exit of the counterpart. 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT command the 'heartbeat at localhost' we were launched to process? 0.000034 [D1] parse_at: 'heartbeat at localhost' in AT command matched the 'heartbeat at localhost' UPSNAME we were launched to process 0.000041 [D1] parse_at: processing CANCEL-TIMER 0.000054 [D2] parse_at: is 'heartbeat at localhost' in AT command the 'heartbeat at localhost' we were launched to process? 0.000057 [D1] parse_at: 'heartbeat at localhost' in AT...

...an exit of the counterpart. 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT command the 'heartbeat at localhost' we were launched to process? 0.000034 [D1] parse_at: 'heartbeat at localhost' in AT command matched the 'heartbeat at localhost' UPSNAME we were launched to process 0.000041 [D1] parse_at: processing CANCEL-TIMER 0.000054 [D2] parse_at: is 'heartbeat at localhost' in AT command the 'heartbeat at localhost' we were launched to process? 0.000057 [D1] parse_at: 'heartbeat at localhost' in AT...

...NOCOMM SYSLOG+WALL+EXEC NOTIFYFLAG NOPARENT SYSLOG+WALL+EXEC RBWARNTIME 43200 NOCOMMWARNTIME 300 INALDELAY 5 the /root/upsmailer is just a simple shell script that mails the events, it looks like: #!/bin/bash RECIPIENT="controller at xxx" SCRIPTNAME=`basename $0` [ `echo $UPSNAME | wc -w` -eq "0" ] && UPSNAME="unknown" [ `echo $NOTIFYTYPE | wc -w` -eq "0" ] && NOTIFYTYPE="unknown" echo "$*" | mailx -s "$SCRIPTNAME: $UPSNAME $NOTIFYTYPE" $RECIPIENT exit 0 When i disconnect the UPS from the power lin...

...device node is > not owned by the NUT gid? > crw-rw-r-- 1 root root 189, 385 Dec 14 12:31 /dev/bus/usb/004/002 It does now. >> Why doesn't "upsdrvctl start" allow nut to find the UPS when it can find it >> without a problem with the options "-u root start <upsname>"? > > The NUT USB drivers use libusb, which need read/write access to the /dev node > for the UPS. The "-u root" hack tells the driver not to drop privileges from > root to the 'nut' system user. > That's what I thought was going on, I just didn'...

On 12/14/2013 12:37 PM, David C. Rankin wrote: > I will test with the new ubs dev permission and report back. Thank you for your > help Charles. Charles, Setting uid:gid to root:nut on /dev/bus/usb/004/002 seemed to be the issue. The question now become how to automate this process so that the user isn't required to manually hunt down the usb dev and change gid to the nut gid? So

...> > > 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT command the > 'heartbeat at localhost' we were launched to process? > 0.000034 [D1] parse_at: 'heartbeat at localhost' in AT command > matched the 'heartbeat at localhost' UPSNAME we were launched to process > 0.000041 [D1] parse_at: processing CANCEL-TIMER > 0.000054 [D2] parse_at: is 'heartbeat at localhost' in AT command the > 'heartbeat at localhost' we were launched to process? > 0.000057 [D1] parse_at: 'heartbeat at...

...> > > 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT command the > 'heartbeat at localhost' we were launched to process? > 0.000034 [D1] parse_at: 'heartbeat at localhost' in AT command > matched the 'heartbeat at localhost' UPSNAME we were launched to process > 0.000041 [D1] parse_at: processing CANCEL-TIMER > 0.000054 [D2] parse_at: is 'heartbeat at localhost' in AT command the > 'heartbeat at localhost' we were launched to process? > 0.000057 [D1] parse_at: 'heartbeat at...

On 12/16/2013 09:06 AM, Charles Lepple wrote: > If you want, we can take a look at the output of the aforementioned udevd > command from your system. Please compress the output, and if the list bounces > it, I'll extract the relevant portion from the bounce message. > > I have a funny feeling we might either have a Debian-specific dependency on > 91-permissions.rules, or