search for: default_logformat

...f the servers down but to let it ride. I also suggest the following patch to upslog.c (little line wrapping there) --- upslog.c.orig 2012-07-31 10:38:58.000000000 -0700 +++ upslog.c 2014-02-20 09:23:14.000000000 -0800 @@ -50,6 +50,7 @@ static flist_t *fhead = NULL; #define DEFAULT_LOGFORMAT "%TIME @Y at m@d @H at M@S% %VAR battery.charge% " \ + "%VAR battery.voltage% %VAR output.current% " \ "%VAR input.voltage% %VAR ups.load% [%VAR ups.status%] " \ "%VAR ups.temperature% %VAR input.frequency%" M...

...battery pack to determine state of charge, it is quite useful to add in the battery pack voltage to the logs as such: --- upslog.c.orig 2012-07-31 10:38:58.000000000 -0700 +++ upslog.c 2014-02-20 09:23:14.000000000 -0800 @@ -50,6 +50,7 @@ static flist_t *fhead = NULL; #define DEFAULT_LOGFORMAT "%TIME @Y at m@d @H at M@S% %VAR battery.charge% " \ + "%VAR battery.voltage% %VAR output.current% " \ "%VAR input.voltage% %VAR ups.load% [%VAR ups.status%] " \ "%VAR ups.temperature% %VAR input.frequency%" T...

...printf(" -u <user> - Switch to <user> if started as root\n"); @@ -371,6 +372,7 @@ char *prog = NULL; const char *user = NULL; struct passwd *new_uid = NULL; + const char *pidfilebase = "upslog"; logformat = DEFAULT_LOGFORMAT; user = RUN_AS_USER; @@ -379,7 +381,7 @@ prog = argv[0]; - while ((i = getopt(argc, argv, "+hs:l:i:f:u:V")) != -1) { + while ((i = getopt(argc, argv, "+hs:l:i:f:u:Vp:")) != -1) { switch(i) { case 'h':...

...rge, it is quite useful to add in the battery pack > voltage to the logs as such: > > --- upslog.c.orig 2012-07-31 10:38:58.000000000 -0700 > +++ upslog.c 2014-02-20 09:23:14.000000000 -0800 > @@ -50,6 +50,7 @@ > static flist_t *fhead = NULL; > > #define DEFAULT_LOGFORMAT "%TIME @Y at m@d @H at M@S% %VAR battery.charge% " \ > + "%VAR battery.voltage% %VAR output.current% " \ > "%VAR input.voltage% %VAR ups.load% [%VAR ups.status%] " \ > "%VAR ups.temperature% %VAR input.frequ...

...ry pack >>> voltage to the logs as such: >>> >>> --- upslog.c.orig 2012-07-31 10:38:58.000000000 -0700 >>> +++ upslog.c 2014-02-20 09:23:14.000000000 -0800 >>> @@ -50,6 +50,7 @@ >>> static flist_t *fhead = NULL; >>> >>> #define DEFAULT_LOGFORMAT "%TIME @Y at m@d @H at M@S% %VAR battery.charge% " \ >>> + "%VAR battery.voltage% %VAR output.current% " \ >>> "%VAR input.voltage% %VAR ups.load% [%VAR ups.status%] " \ >>> "%VAR ups.temperature% %VAR input.frequency%" >>>...

...quite useful to add in the battery pack >> voltage to the logs as such: >> >> --- upslog.c.orig 2012-07-31 10:38:58.000000000 -0700 >> +++ upslog.c 2014-02-20 09:23:14.000000000 -0800 >> @@ -50,6 +50,7 @@ >> static flist_t *fhead = NULL; >> >> #define DEFAULT_LOGFORMAT "%TIME @Y at m@d @H at M@S% %VAR battery.charge% " \ >> + "%VAR battery.voltage% %VAR output.current% " \ >> "%VAR input.voltage% %VAR ups.load% [%VAR ups.status%] " \ >> "%VAR ups.temperature% %VAR input.frequency%" >> > > 1. I...

On Feb 19, 2014, at 12:50 PM, Ted Mittelstaedt wrote: > Worse, however, is if there's a power failure right near the end > of the 2-days-off cycle. That happened to me last week - it was a > short duration 15 second loss - and the upscode2 driver decided it needed to issue a forced shutdown. > > Very likely this was because upscode2 had decided the batteries > were

...- Switch to <user> if started as root\n"); > @@ -372,6 +373,7 @@ > time_t now, nextpoll = 0; > const char *user = NULL; > struct passwd *new_uid = NULL; > + const char *pidfilebase = "upslog"; > > logformat = DEFAULT_LOGFORMAT; > user = RUN_AS_USER; > @@ -380,7 +382,7 @@ > > prog = argv[0]; > > - while ((i = getopt(argc, argv, "+hs:l:i:f:u:V")) != -1) { > + while ((i = getopt(argc, argv, "+hs:l:i:f:u:Vp:")) != -1) { > switch(i) { >...

...to the logs as such: >>>> >>>> --- upslog.c.orig 2012-07-31 10:38:58.000000000 -0700 >>>> +++ upslog.c 2014-02-20 09:23:14.000000000 -0800 >>>> @@ -50,6 +50,7 @@ >>>> static flist_t *fhead = NULL; >>>> >>>> #define DEFAULT_LOGFORMAT "%TIME @Y at m@d @H at M@S% %VAR battery.charge% >>>> " \ >>>> + "%VAR battery.voltage% %VAR output.current% " \ >>>> "%VAR input.voltage% %VAR ups.load% [%VAR ups.status%] " \ >>>> "%VAR ups.temperature% %VAR input....

Hi, Am 13.02.2012 um 18:58 schrieb Arnaud Quette: > 2012/2/6 thomas schorpp <thomas.schorpp at googlemail.com>: >> Hi, > > Hi Thomas, > >> I want the driver report the battery status from ABM charging controllers >> -patch attached- : > > For now, I've tracked your patch here: >

Hi All, I have what is probably a 12 year old (or older) Compaq R3000 UPS plugged into a FreeBSD 8 system running NUT version 2.6.5 This UPS contains a total of 16 batteries in 2 banks of 8, each battery is 6 volts and the bank produces 50 volts. The UPS monitors battery voltage and the battery charger in the UPS works like this. For about 2 days it will apply a charge/float/topping

2012/2/6 thomas schorpp <thomas.schorpp at googlemail.com>: > Hi, Hi Thomas, > I want the driver report the battery status from ABM charging controllers > -patch attached- : thanks for your patch. since it introduces a new variable (battery.status.abm), I prefer to step back and think to something useful more widely. thus, I'm thinking about a generic

...%s\n", - UPS_VERSION); + upsversion()); exit(EXIT_SUCCESS); case 'h': Index: clients/upslog.c =================================================================== --- clients/upslog.c (revision 916) +++ clients/upslog.c (working copy) @@ -375,7 +375,7 @@ logformat = DEFAULT_LOGFORMAT; user = RUN_AS_USER; - printf("Network UPS Tools upslog %s\n", UPS_VERSION); + printf("Network UPS Tools upslog %s\n", upsversion()); prog = argv[0]; Index: clients/upsmon.c =================================================================== --- clients/upsmon.c (revis...