similar to: Reduce frequency of upsd /var/log/messages

Hi Larry, [please use reply-all to include the list - the NUT lists do not add a reply-to header.] On Oct 21, 2015, at 3:23 PM, Larry Baker <baker at usgs.gov> wrote: > > I use the NUT RPM package for CentOS 6.7, which is version 2.6.5-2. I admit I am not too familiar with the RH/CentOS family these days. Is there a CentOS site for keeping tabs on the NUT RPMs, or is it sufficient

I use the NUT RPM package for CentOS 6.7, which is version 2.6.5-2. I am testing implementation of NUT features with APC and Tripp-Lite USB UPS interfaces. Things are going reasonably well. However, I'm seeing many more messages than I would like in /var/log/messages when I boot the system without the UPS connected (testing a failure scenario). I have configured NOCOMMWARNTIME 3600, which

I use the NUT RPM package for CentOS 6.7, which is version 2.6.5-2. I am testing implementation of NUT features with APC and Tripp-Lite USB UPS interfaces. Things are going reasonably well. However, I'm seeing many more messages than I would like in /var/log/messages when I boot the system without the UPS connected. I have configured NOCOMMWARNTIME 3600, which takes care to only broadcast

That is terminology from Computer Science. (Decades ago?) It is familiar. Not invented by Cisco. As in, producer-consumer, from the same time. Those were all different paradigms for client-server relationships. There must be Wikipedia citations that can be consulted. As I recall, there were distinctions, such as, producer-consumer were tightly bound, where the producer had no purpose

That is terminology from Computer Science. (Decades ago?) It is familiar. Not invented by Cisco. As in, producer-consumer, from the same time. Those were all different paradigms for client-server relationships. There must be Wikipedia citations that can be consulted. As I recall, there were distinctions, such as, producer-consumer were tightly bound, where the producer had no purpose

There is, https://en.m.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern I said I stayed away from it because of the Cisco link. Others as well as you are free to persue it. I was just making suggestions. On Fri, Mar 12, 2021, 10:43 PM Baker, Lawrence M <baker at usgs.gov> wrote: > That is terminology from Computer Science. (Decades ago?) It is > familiar. Not invented by

There is, https://en.m.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern I said I stayed away from it because of the Cisco link. Others as well as you are free to persue it. I was just making suggestions. On Fri, Mar 12, 2021, 10:43 PM Baker, Lawrence M <baker at usgs.gov> wrote: > That is terminology from Computer Science. (Decades ago?) It is > familiar. Not invented by

Hello all, As some people watching GitHub closely might have noticed, the majority of proposed changes (for primary/secondary in the end) were merged around weekend. This impacts text documentation and keyword support for upsmon configuration, testing welcome :) Some work remains for image files in documentation, and the protocol/ABI were not touched so far. Following the recent eminent

Hello all, As some people watching GitHub closely might have noticed, the majority of proposed changes (for primary/secondary in the end) were merged around weekend. This impacts text documentation and keyword support for upsmon configuration, testing welcome :) Some work remains for image files in documentation, and the protocol/ABI were not touched so far. Following the recent eminent

Thank you for the suggestions, keep them coming :) To me, I think I considered pub-sub but it did not quite fit - gotta refresh my memory by code re-reading (or expert comments) - I found I'm vague now on who hits the big red button to shout that a particular power source device got critical - the upsmon in "master" role, or "upsd" that talks to all subscribed (indeed!)

Thank you for the suggestions, keep them coming :) To me, I think I considered pub-sub but it did not quite fit - gotta refresh my memory by code re-reading (or expert comments) - I found I'm vague now on who hits the big red button to shout that a particular power source device got critical - the upsmon in "master" role, or "upsd" that talks to all subscribed (indeed!)

So, for the past couple of days the SurveyMonkey results are not changing, with 13 replies overall. Should we wait for more or everyone passionate enough has already spoken? In practice I'd likely follow up on a weekend anyway, but... the weekend is coming! :) Currently we have a clear leader pair that collected almost half the votes (6), two votes were to keep old words in place - alas,

So, for the past couple of days the SurveyMonkey results are not changing, with 13 replies overall. Should we wait for more or everyone passionate enough has already spoken? In practice I'd likely follow up on a weekend anyway, but... the weekend is coming! :) Currently we have a clear leader pair that collected almost half the votes (6), two votes were to keep old words in place - alas,

Jim, The terminology I recall for that one-to-many relationship is publisher-subscriber. Larry Baker US Geological Survey 650-329-5608 baker at usgs.gov<mailto:baker at usgs.gov> On Mar 12 2021, at 6:24:38 PM, Phil Stracchino via Nut-upsuser <nut-upsuser at alioth-lists.debian.net<mailto:nut-upsuser at alioth-lists.debian.net>> wrote: This email has been received from

Jim, The terminology I recall for that one-to-many relationship is publisher-subscriber. Larry Baker US Geological Survey 650-329-5608 baker at usgs.gov<mailto:baker at usgs.gov> On Mar 12 2021, at 6:24:38 PM, Phil Stracchino via Nut-upsuser <nut-upsuser at alioth-lists.debian.net<mailto:nut-upsuser at alioth-lists.debian.net>> wrote: This email has been received from

I didn't go there due to its use by Cisco. On Fri, Mar 12, 2021, 10:03 PM Baker, Lawrence M via Nut-upsuser < nut-upsuser at alioth-lists.debian.net> wrote: > Jim, > > The terminology I recall for that one-to-many relationship is > publisher-subscriber. > > Larry Baker > US Geological Survey > 650-329-5608 > baker at usgs.gov > > > > On Mar 12

I didn't go there due to its use by Cisco. On Fri, Mar 12, 2021, 10:03 PM Baker, Lawrence M via Nut-upsuser < nut-upsuser at alioth-lists.debian.net> wrote: > Jim, > > The terminology I recall for that one-to-many relationship is > publisher-subscriber. > > Larry Baker > US Geological Survey > 650-329-5608 > baker at usgs.gov > > > > On Mar 12

i have posted this question couple of times and never really got any hits i wasn't able to provide any debug info Connected to Asterisk 1.6.0.21 currently running on phoneserver (pid = 3309) Verbosity is at least 4 == Using SIP RTP TOS bits 184 == Using SIP RTP CoS mark 5 == Using SIP VRTP TOS bits 136 == Using SIP VRTP CoS mark 6 == Extension Changed 117[ext-local] new

Hello, I'm facing problems as I'm installing NUT to monitor a MGE Ellipse ASR600USBS on a FreeBSD 6.1 box. UPS is recognized as : ugen0: MGE UPS SYSTEMS ELLIPSE, rev 1.10/42.41, addr 2 I'm temporarily using root profile (devfs/devd scripts not modified atm). newhidups starts & runs fine (unplugging mains makes newhidups outputs lots of data when started with -DDDD flags)

Just noticed that I get a similar error about object 'kronecker' in "Matrix" package when trying to load "lme4". So this is a more pervasive problem. Brian Brian S. Cade, PhD U. S. Geological Survey Fort Collins Science Center 2150 Centre Ave., Bldg. C Fort Collins, CO 80526-8818 email: brian_cade@usgs.gov tel: 970 226-9326 ----- Forwarded by Brian S