search for: lb

...ase this later. */ -#define LINEBUF_SIZE 16 - -typedef struct { - char *buf; - u_int size; - int lineno; - const char *filename; - FILE *stream; - void (*errfun) (const char *,...); -} Linebuf; - -static Linebuf * -Linebuf_alloc(const char *filename, void (*errfun) (const char *,...)) -{ - Linebuf *lb; - - if (!(lb = malloc(sizeof(*lb)))) { - if (errfun) - (*errfun) ("linebuf (%s): malloc failed\n", - filename ? filename : "(stdin)"); - return (NULL); - } - if (filename) { - lb->filename = filename; - if (!(lb->stream = fopen(filename, "r"))) { -...

Hi few typos i've found ?.C Specifying 'ENCODING' overrrides any declared encodings (see 'link{Encoding}') \link{Encoding} -------------------- writing R extensions, pag 73 (pdf version), note 1, and we provided an emulation on Windows 2000): see ?dyn.oad ^ ^^ 1

Carsten Aulbert <carsten.aulbert at aei.mpg.de> writes: > Hi all, > > On 5/19/23 15:11, Greg Troxel wrote: >> LB is baked in to nut behavior. So if a UPS doesn't report LB, then >> it makes sense to synthesize it. Synthetic LB is the cleanest fix at >> the earli...

My $0.02: LB is baked in to nut behavior. So if a UPS doesn't report LB, then it makes sense to synthesize it. Synthetic LB is the cleanest fix at the earlier processing point. One could have a config that is basically synthetic-lowbatt-percent that generates LB if (as Jim says) on battery,...

Hi all, On 5/19/23 15:11, Greg Troxel wrote: > LB is baked in to nut behavior. So if a UPS doesn't report LB, then > it makes sense to synthesize it. Synthetic LB is the cleanest fix at > the earlier processing point. I fully agree and thus this ought to be done in/near uspd IMHO. I glanced over the server/ directory and was n...

...orking at stop "send: QS". The debug logs show values successfully >> retrieved repeatedly until something like: >> .... >> Quick update... >> send: QS >> read: (247.9 239.1 248.0 005 50.0 27.5 --.- 00001001 >> update_status: OL >> update_status: !LB >> update_status: !CAL >> update_status: !FSD >> upsdrv_updateinfo... >> Quick update... >> send: QS >> (driver hangs here) >> >> I'm using Generic Q* USB/Serial driver 0.06 (2.7.2) with USB >> communication driver 0.32. Playing with pollint...

Hmm. Is there maybe something there already that will do this? Maybe kind of back-handed. In drivers/dstate.c, I see: In status_init(), if ?driver.flag.ignorelb? is set in the driver state, the ?ignorelb? flag is set. In status_set(), if ignorelb is set, and the status being set (presumably from the UPS) is LB, it?s ignored. In other words, LB reported by the UPS is ignored. In status_commit(), if ignorelb is set, there?s code to compare battery.charge aga...

...he batteries could still hold as charge was 30 % with about > 15 minutes run time. And the UPS did hold for another full 10 minutes > before powering off. These are the relevant lines from /var/log/ups: > > 20200124 201318 32 0.0 12 [OB] NA 0.0 > 20200124 201323 30 0.0 13 [ALARM OB LB] NA 0.0 > 20200124 201328 30 0.0 13 [FSD ALARM OB LB] NA 0.0 > 20200124 201333 30 0.0 13 [FSD ALARM OB LB] NA 0.0 > 20200124 201338 30 0.0 13 [FSD ALARM OB LB] NA 0.0 > 20200124 201340 30 0.0 13 [FSD ALARM OB LB] NA 0.0 that looks perfectly fine > > The server was shutdown prop...

...en will randomly stop > working at stop "send: QS". The debug logs show values successfully > retrieved repeatedly until something like: > .... > Quick update... > send: QS > read: (247.9 239.1 248.0 005 50.0 27.5 --.- 00001001 > update_status: OL > update_status: !LB > update_status: !CAL > update_status: !FSD > upsdrv_updateinfo... > Quick update... > send: QS > (driver hangs here) > > I'm using Generic Q* USB/Serial driver 0.06 (2.7.2) with USB communication > driver 0.32. Playing with pollinterval didn't help - Is there any...

...e test? Should I >disable >SHUTDOWNCMD in upsmon.conf? Or is there any other way to ignore forced >shutdown? I'd like to see how long it would go until the batteries >actually drain. > Disconnect the computer from the UPS, connect a dummy load (like 2-3 * 100W tungsten light bulbs) , turn off the nut client on the computer. Start a stopwatch. Unplug the UPS from mains and wait for it to die. Read the value on the stopwatch. wolfy

Hi again, On 5/22/23 18:31, Willcox David via Nut-upsuser wrote: > Hmm. Is there maybe something there already that will do this? Maybe > kind of back-handed. > > In drivers/dstate.c, I see: > > 1. In status_init(), if ?driver.flag.ignorelb? is set in the driver > state, the ?ignorelb? flag is set. > 2. In status_set(), if ignorelb is set, and the status being set > (presumably from the UPS) is LB, it?s ignored. In other words, LB > reported by the UPS is ignored. > 3. In status_commit(), if ignorelb is se...

Makes sense, and a PR is a way to solicit feedback :) I'd document this for ups.conf (man page and examples), including a note that for devices which do provide a healthy LB these values may be set to 0 safely. Wondering if non-zero defaults should be there anyway. @Community, WDYT? Also, this critical-state check should be done only when the UPS is on battery (and perhaps not calibrating), to avoid shutdowns as soon as we start after an outage :) (In a similar fashio...

Hello, when I run on my proxy server: # puppet device --debug --deviceconf /etc/puppet/device/F5-lb-test.conf I get this error: info: starting applying configuration to F5-lb-test at https://operating:operating4lbtest@F5-lb-test/Common debug: Puppet::Device::F5: connecting to F5 device F5-lb-test. debug: Puppet::Device::F5: connecting to partition Common. *err: Can''t load f5 for F5-lb-...

...with it through mge-shut, it detects correctly when on battery. I am using Nut 2.0.3 on Linux (RHEL 3). I am trying to simulate a low battery condition to test my shutdown procedure by setting lowbatt to 98%: driver.parameter.lowbatt: 98 but the ups reaches this value, goes to 97% and still no LB. I tried to change, in the ups firmware, the threshold for pre-alarm to 98% and the ups started its shutdown sequence however nut would still not get LB in ups.status so no shutdown. Any ideas I do not get the LB status ? I cannot wait for the batteries to reach 20% charge to see if it works tha...

...s encountered batteries that were ok, but at times one of the > cells would develop a random short/open, therefore reducing the real > capacity even if voltage reading was ok. In the absence of a battery load > tester i would suggest running multiple tests with a load (car headlight > bulb or similar) on the battery outside the ups. This is to eliminate the > suspicion of a software or UPS unit fault. > > Alex. > > On Mon, 27 Jan 2020, 02:53 Manuel Wolfshant, <wolfy at nobugconsulting.ro> > wrote: > > > On 1/25/20 10:53 AM, Georgi D. Sotirov wrote: &g...

Hmm, looking at status_commit(), if the UPS actually reported just ?OB", but the ?ignorelb? logic kicked in, wouldn?t status_commit() change it to ?OB LB?? And would clients interpret that correctly? And, assuming status_commit() is called, is the status so saved what?s returned on a future client query? I?m really unsure how all of this works. I don?t suppose there?s some kind of ?ge...

An embedded and charset-unspecified text was scrubbed... Name: inte tillg?nglig Url: https://stat.ethz.ch/pipermail/r-help/attachments/20070103/d0f3260e/attachment.pl

...cs package] Hi, I am currently running a lengthy simulation study (no details necessary) on a large multi-core system. The simulated data sets are stored in a long list and they are unevenly sized (hence, the computation times vary greatly between data sets), so I naively thought that parLapplyLB() would be the right function to parallelize my computations. Presently, only two thirds of my computations are finished, however, only 16 of my 72 workers seem to be active, whereas the remaining 56 seem to run idle. I tried to find out in more detail what parLapplyLB() actually does and I wa...

Hello. I sometimes encountered batteries that were ok, but at times one of the cells would develop a random short/open, therefore reducing the real capacity even if voltage reading was ok. In the absence of a battery load tester i would suggest running multiple tests with a load (car headlight bulb or similar) on the battery outside the ups. This is to eliminate the suspicion of a software or UPS unit fault. Alex. On Mon, 27 Jan 2020, 02:53 Manuel Wolfshant, <wolfy at nobugconsulting.ro> wrote: > On 1/25/20 10:53 AM, Georgi D. Sotirov wrote: > > OK, so yesterday evening I do...

I am using nut 2.2.2 and I have a CyberPower CP550SL. According to the drivers list, I should be using genericups with upstype set to 7, but when I try that and when I run upsc I get: driver.name: genericups driver.parameter.LB: 04 driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ups driver.parameter.upstype: 7 driver.version: 2.2.2 driver.version.internal: 1.34 ups.mfr: CyberPower ups.model: Power99 ups.status: LB OB Even through I'm on line (A/C) power and my battery is charged. I have also tried the c...