similar to: NUT on Windows Clients

Displaying 20 results from an estimated 4000 matches similar to: "NUT on Windows Clients"

2021 Mar 13
1
[EXTERNAL] Re: On retiring some terminology
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
2021 Mar 13
1
[EXTERNAL] Re: On retiring some terminology
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
2021 Mar 13
1
[EXTERNAL] Re: On retiring some terminology
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
2021 Mar 13
1
[EXTERNAL] Re: On retiring some terminology
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
2021 Mar 13
1
[EXTERNAL] Re: On retiring some terminology
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!)
2021 Mar 13
1
[EXTERNAL] Re: On retiring some terminology
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!)
2021 Mar 13
1
[EXTERNAL] Re: On retiring some terminology
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
2021 Mar 13
1
[EXTERNAL] Re: On retiring some terminology
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
2021 Mar 18
1
[EXTERNAL] Re: On retiring some terminology
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,
2021 Mar 18
1
[EXTERNAL] Re: On retiring some terminology
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,
2021 Mar 13
1
On retiring some terminology
On 3/12/21 9:14 PM, Rusty Bower wrote: > Manager/subscriber seems most accurate > > Sent from my iPhone > >> On Mar 12, 2021, at 20:13, Douglas Parsons <doug at parsonsemail.com> wrote: >> >> ? >> In place of secondary how about subscriber? It would be accurate to >> the role. I'd been going to suggest controller and ... something.
2021 Mar 13
1
On retiring some terminology
On 3/12/21 9:14 PM, Rusty Bower wrote: > Manager/subscriber seems most accurate > > Sent from my iPhone > >> On Mar 12, 2021, at 20:13, Douglas Parsons <doug at parsonsemail.com> wrote: >> >> ? >> In place of secondary how about subscriber? It would be accurate to >> the role. I'd been going to suggest controller and ... something.
2021 Mar 13
1
[EXTERNAL] Re: On retiring some terminology
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
2021 Mar 13
1
[EXTERNAL] Re: On retiring some terminology
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
2010 Mar 26
5
Tripp Lite SmartOnline 3U
I have the following UPS that I'm trying to get to work with NUT: SU3000RTXL3U I have it connected via USB. My ups.conf looks like: [test] driver = usbhid-ups vendorid = 09ae port = auto When I run upsdrvctl -DD start, I get: Network UPS Tools - UPS driver controller 2.4.1 Starting UPS: test exec: /lib/nut/usbhid-ups -a test Network UPS Tools - Generic HID driver 0.34 (2.4.1)
2012 Aug 30
1
Force Shutdown without shuting down the UPS
I have NUT server connected to the UPS, several other servers connects to this server, after 5 minutes without power I want all the servers to shutdown without waiting to the UPS batt status. Everything works ok, but I have one issue, the NUT server shutdown the UPS unit too, this is ok in most case but in our case I don't want the UPS to be shutdown. All the servers yes and the NUT server
2020 Jan 13
3
Help needed with NUT installation on Windows 10
Hello, My setup is a Windows 10 machine, NUT installed from latest MSI. UPS is Advice PRV650 connected with a USB cable. I think the relevant log lines are: C:\Program Files (x86)\NUT\bin>nut-scanner.exe Cannot load USB library (libusb) : The specified module could not be found.. USB search disabled. I have tried to install winusb driver using zadig utility without any success (the utility
2013 Sep 17
0
Support for APC Smart-UPS X 3000
Just my experiences speaking, look at another brand. I use MGE/Eaton and have had much better life and the quality has been much better. APC does not release the protocol for comunicating with the UPS and so to get NUT to work you have to sniff the traffic and then figure out what the commands and responses mean.(thus reverse engineered) APC also will change the protocol between models. (Thus why
2013 Sep 17
4
Support for APC Smart-UPS X 3000
Hi all, I am completely new to NUT and setting up a UPS shut down in Linux. I am looking at buying a APC Smart-UPS X 3000. When I look this device up in the compatibility list this specific model is not listed, only a generic entry for "Smart-UPS". It says to use the *apcsmart* driver. The legend shows this as "protocol based on reverse engineering". What does this
2009 Feb 13
3
early shutdown of VMware VMs
I'm new to NUT, but didn't find a clear answer to this either in the recent "ordered shutdown" thread or in Google: How to shut down VMWare guest virtual machines earlier than the host machine they run on? (For example, if everything normally shuts down at 5% UPS battery, then the VMs should shut down at 10%.) I also read upssched.txt but I can't tell from the early