search for: clear_alarm

...he down > remote host... It eventually gave up - but since the 2 minute timeout was > pretty long - it also marked all other UPSes it was monitoring as "down" > (and then immediately "up" again). Causing a lot of unncessary > false alarms... Solved with a set_alarm()/clear_alarm() wrapper around the > upscl_connect() call. > thanks for your patch. I've got to check it more thoroughly, but it will at least need some rework. as an example, the "signal(SIGCHLD, SIG_IGN)" should be in "setup_signals(void)" and use "sigaction" for more p...

...R2"; + query[1] = ups->upsname; + numq = 2; + } + if (!strcmp(var, "status")) { query[0] = "VAR"; query[1] = ups->upsname; @@ -1518,7 +1530,25 @@ static void pollups(utype_t *ups) if (get_var(ups, "status", status, sizeof(status)) == 0) { clear_alarm(); parse_status(ups, status); - return; + /* All is well, continue to poll SIGUSR1 RP */ + set_alarm(); + if (get_var(ups, "SIGUSR1", status, sizeof(status)) == 0) { + clear_alarm(); + if ( ! (strcmp(status,"0") == 0)) { /* See K&R p.53 */ + /* We have a...

...debug("polling ups: %s\n", ups->sys); > > +//EW >>>>>> > + /* if the user wants us to check for overtemp */ > + if (upsovertemp > 0.0) { > + set_alarm(); > + > + if (get_var(ups, "temp", status, sizeof(status)) == 0) { > + clear_alarm(); > + parse_temperature(ups, status); > + } > + > + /* fallthrough: no communications */ > + clear_alarm(); > + } > +//EW <<<<<< > + > set_alarm(); > > > > +++ upsmon.config (changes somewhere in the config file) > > # ----...