search for: upsdrv_shutdown

Hi all, Arjen can you enlighten me about the function of the blazer upsdrv_shutdown function. I think they are in the wrong order. Regards Kjell

while finishing some work on the HAL integration (I'm now mapping DBus method with NUT commands, to allow at least the final UPS poweroff), I was horrified to realize (and so late) the changes in usbhid-ups->upsdrv_shutdown(). We've lost a lot there, but making a generic code, instead of keeping the subdrivers delegation. For example, the shutdown.return command (which is or should be the standard UPS poweroff method) has to set both delay.shutdown *and* delay.start does only set the latter. It results in an imm...

...> ups.StatusUPS) ; > 900 dstate_setinfo("ups.ShortStatus", "%04X", > ups.ShortStatus) ; > 905 dstate_setinfo("ups.time", "%02d:%02d:%02d", > p[6], p[7], p[8]) ; The above is a waste of effort. By the time upsdrv_shutdown() runs, the server won't be listening anymore. > 958 addvar(VAR_VALUE, "ups.delay.shutdown", "Override > shutdown delay (120s)"); > 959 addvar(VAR_VALUE, "ups.delay.start", "Override restart > delay (10s)"); This does...

...e_getinfo when checking if it were true... I'm *really* not sure why I did... probably excess blood in my caffeine stream at the time! ;-) ) - the second change removed the function I'd introduced to perform the original "shutdown and hope" behaviour. The code is now back in upsdrv_shutdown() at the end and now looks like this: upsdrv_shutdown() /* decide if we're in waitonshutdown and set wos=1 if we are ... */ if (wos) { /* waitonshutdown: prepare things for going into belkin_wait() ... */ belkin_wait() upslogx(LOG_WARNING, " bel...

Hi, I started updating smart driver with a few things I've been missing. While going through the source: - in upsdrv_shutdown(), there're loads of printfs - they kinda look like a leftover from older debug times. Shouldn't they be changed into upsdebugx() or upslogx() ?

...as Jarosch <thomas.jarosch at intra2net.com> --- drivers/mge-utalk.c | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/drivers/mge-utalk.c b/drivers/mge-utalk.c index c6114c7..616e2ad 100644 --- a/drivers/mge-utalk.c +++ b/drivers/mge-utalk.c @@ -465,7 +465,8 @@ void upsdrv_shutdown(void) { char buf[BUFFLEN]; /* static time_t lastcmd = 0; */ - + memset(buf, 0, sizeof(buf)); + if (sdtype == SD_RETURN) { /* enable automatic restart */ mge_command(buf, sizeof(buf), "Sx 5"); -- 1.7.4.4

...Aan: adkorte-guest at alioth.debian.org Hi, I apologize if you are not the correct person, but I was wanting to submit a bug report for the upscode2.c driver but could not find a way to do that from the NUT website. Here is the problem code and what I have noticed in upscode2.c: void upsdrv_shutdown(void) { if (can_upsd && can_uppc) { upslogx(LOG_EMERG, "Emergency shutdown"); upscsend("UPSD"); /* Set shutdown delay */ upscsend("1"); /* 1 second (lowest possible. 0 returns current....

...gress test.panel.start - Start testing the UPS panel test.panel.stop - Stop a UPS panel test The last lines of output from 'usbhid-ups -DDDD -a apc -k': Path: UPS.PowerSummary.AudibleAlarmControl, Type: Feature, ReportID: 0x14, Offset: 0, Size: 8, Value: 2.000000 Initiating UPS shutdown upsdrv_shutdown... instcmd(shutdown.return, [NULL]) find_nut_info: unknown info type: shutdown.return instcmd(load.on.delay, 5) find_nut_info: unknown info type: load.on.delay instcmd: info element unavailable load.on.delay instcmd(shutdown.reboot, [NULL]) Can't set Report 19: Broken pipe instcmd: FAILED Shutd...

...river ignores my setting, and forces UPSD to have a value of "1" just before issuing the UPPC shutdown command. Removing this UPSD allows the custom value to be used correctly. Also I changed the shutdown messages so the ups.delay.* values are reported. With all that, here's what upsdrv_shutdown looks like: void upsdrv_shutdown(void) { if (upsc_commandlist()) { if (!can_upsd || !can_uppc) { fatalx(LOG_EMERG, "Shutdown called, but UPS does not support it"); } } else { upslogx(LOG_EMERG, "Can't determine if shutdown is supported, attempting anyway"); }...

Gentlemen, I have done some experiments with an APC Back-UPS ES 650, to identify the currently specified items that are not available with this device, and to find out what non-standard items the device provides. Of the currently specified items, the following are not available: UPS.Battery.Temperature UPS.Output.PercentLoad UPS.PowerSummary.DelayBeforeShutdown UPS.Battery.Test

...tID: 0002 - Manufacturer: American Power Conversion - Product: Back-UPS BR 800 FW:9.o4 .I USB FW:o4 - Serial Number: 3B0730X30508 - Bus: 001 Trying to match device Device matches HID descriptor length 1217 Report Descriptor size = 1217 Using subdriver: APC HID 0.92 [cut] Initiating UPS shutdown upsdrv_shutdown... instcmd(shutdown.return, [NULL]) find_nut_info: unknown info type: shutdown.return instcmd(load.on.delay, 30) find_nut_info: unknown info type: load.on.delay instcmd: info element unavailable load.on.delay instcmd(shutdown.reboot, [NULL]) Can't set Report 19: Broken pipe Shutdown failed!...

...to low battery, but none turned off when the UPS went critical. Given the range of hardware involved, this must be a common software problem. The systems will shut down properly if I do "upsmon -c fsd", so it doesn't appear to be a permissions problem. I don't think this is the upsdrv_shutdown() issue described in the snmp-ups man page; I do not care if the UPS shuts down when the computer does, nor do I want it to. I just want upsmon to shut down the system when the UPS goes critical. Here are my config files; the system is tanya, its UPS is tanya-ups. Any advice? ups.conf: [tanya-up...

Cheers, With https://github.com/networkupstools/nut/pull/1906 and https://github.com/networkupstools/nut/pull/1912 (and probably some more later), I've been enhancing NUT driver framework with support for live reload of configuration, primarily to acknowledge changes to debug_min setting in ups.conf - but made in a generic fashion that specific drivers may take advantage of for their

Cheers, With https://github.com/networkupstools/nut/pull/1906 and https://github.com/networkupstools/nut/pull/1912 (and probably some more later), I've been enhancing NUT driver framework with support for live reload of configuration, primarily to acknowledge changes to debug_min setting in ups.conf - but made in a generic fashion that specific drivers may take advantage of for their

Hi all! As I'm currently porting the HP PowerTrust driver from nut-1.4.3, I have a question regarding ups.delay.*. The PTs can delay the Shutdown/Restart and Kill commands by an arbitrary number of seconds, i.e. they wait for n seconds and then shutdown or kill. The delay for the restart after the shutdown can't be changed. Which of the ups.delay.* variables correspond to these values?

..._signals': genericups.c:66:9: error: invalid operands to binary | (have 'int' and 'struct <anonymous> *') *line |= TIOCM_ST; ^ genericups.c:66:3: warning: statement with no effect [-Wunused-value] *line |= TIOCM_ST; ^ genericups.c: In function 'upsdrv_shutdown': genericups.c:280:12: warning: comparison between pointer and integer if (flags == TIOCM_ST) { ^ Makefile:1448: recipe for target 'genericups.o' failed make[1]: *** [genericups.o] Error 1 make[1]: Leaving directory '/cygdrive/c/nut/drivers' Makefile:513: re...

On Sat, May 28, 2016 at 11:05 AM, abi <abi at abinet.ru> wrote: > However I was unable to shutdown.return it. Maybe protocol is not fully > compatible? > > 0.145757 Initiating UPS shutdown > 0.145760 upsdrv_shutdown... > 0.145763 instcmd(shutdown.return, [NULL]) > 0.145767 powercom_shutdown_nuf: value = (null), command = 5400 > 0.145770 hu_find_valinfo: found 21504 (value: (null)) > 0.145773 Unit = 00000000, UnitExp = 0 > 0.145775 Exponent = 0 > 0.145778 Ph...

...e: > On Sat, May 28, 2016 at 11:05 AM, abi <abi at abinet.ru > <mailto:abi at abinet.ru>> wrote: > > However I was unable to shutdown.return it. Maybe protocol is not > fully compatible? > > 0.145757 Initiating UPS shutdown > 0.145760 upsdrv_shutdown... > 0.145763 instcmd(shutdown.return, [NULL]) > 0.145767 powercom_shutdown_nuf: value = (null), command = 5400 > 0.145770 hu_find_valinfo: found 21504 (value: (null)) > 0.145773 Unit = 00000000, UnitExp = 0 > 0.145775 Exponent = 0 &g...

...l shutdown from a secondary server acting as a master for the repeated driver (which is pretending to run out of battery early) you DONT want it forwarding this command back to the real driver and turning that off. I looked at the driver src and it fortunately appears to be safe - but only because upsdrv_shutdown is not supported when called from the init.d scripts during poweroff. If that was ever to change then the result would depend on what was actually implemented. I suspect there might be instcmds that might be risky to forward too when the driver is used in this mode. These are OK at present as for...

On Dec 20, 2017, at 10:32 AM, Ken Olum wrote: > > 0.090564 find_nut_info: unknown info type: load.on.delay > 0.090577 find_nut_info: unknown info type: load.on.delay > 0.090585 Initiating UPS shutdown > 0.090593 upsdrv_shutdown... > 0.090601 instcmd(shutdown.return, [NULL]) > 0.090614 find_nut_info: unknown info type: shutdown.return > 0.090624 instcmd(load.on.delay, [NULL]) > 0.090633 find_nut_info: unknown info type: load.on.delay > 0.090641 instcmd: info element unavailable load.on.delay >...