search for: olum

...n the OpenSSH development list (Cc'ed here). There is a patch call out right now for the pending release of 2.4.0. I'm wondering if anyone is aware of this and if it's already been covered in 2.4.0? Please reply to list and original poster... ----- Forwarded message from Ken Olum <kdo at cosmos.phy.tufts.edu> ----- Date: Wed, 27 Dec 2000 16:19:20 -0500 From: Ken Olum <kdo at cosmos.phy.tufts.edu> To: ssh at clinet.fi Subject: protocol incompatibility between OpenSSH and SSH secure shell? Precedence: bulk I am using SSH secure shell version 2.3 under Windows 95...

On Jan 22, 2018, at 3:00 PM, Ken Olum <kdo at cosmos.phy.tufts.edu> wrote: > > I tested the effect of setting UPS.OutletSystem.Outlet.DelayBeforeShutdown > using Tripp Lite's software, which appears to be as follows: > Theoretically, this should be the same as running the command "upscmd bcpers at localhost...

Thanks Ken. I'll plan to sit down and look up the protocol information over the next week or so and follow up. ________________________________ From: Ken Olum <kdo at cosmos.phy.tufts.edu> Sent: Tuesday, January 14, 2020 1:35:10 PM To: David Zomaya Cc: kdo at cosmos.phy.tufts.edu; layne.fowler at gmail.com; nut-upsuser at alioth-lists.debian.net Subject: [EXTERNAL] Re: [Nut-upsuser] Tripp Lite SMART1500LCD will not stay shut down when power is disc...

...the shutdown.stayoff logic? https://github.com/networkupstools/nut/blob/master/drivers/usbhid-ups.c#L562 This might be a dumb question but did this require you to recompile the kernel? These types of changes are way beyond my depth. Thank you for the direction! On Thu, Jan 2, 2020, 11:38 AM Ken Olum <kdo at cosmos.phy.tufts.edu> wrote: > Hi, Layne. I had a similar problem with my Tripp-Lite BCPERS450. You > can see the previous correspondence by searching for > > site:alioth-lists.debian.net/pipermail/nut-upsuser BCPERS450 shutdown > > with Google. > > In parti...

...nitdir=/lib/systemd/system \ --with-systemdshutdowndir=/lib/systemd/system-shutdown make make check VERBOSE=1 cd ~/nut/drivers sudo upsdrvctl stop sudo make install sudo apt remove nut-build-deps sudo apt remove devscripts sudo apt autoremove sudo upsdrvctl start On Sat, Jan 4, 2020 at 5:15 PM Ken Olum <kdo at cosmos.phy.tufts.edu> wrote: > From: Layne Fowler <layne.fowler at gmail.com> > Date: Fri, 3 Jan 2020 16:22:10 -0500 > > I see, so you kept the load.on.delay command but removed the check to > see > if it was handled. Did you do the same thing for...

...rial number and the corner-cases you don't have answers for and I can look into it. Thank you, David Zomaya Tripp Lite david_zomaya at tripplite.com -----Original Message----- From: Nut-upsuser <nut-upsuser-bounces+david_zomaya=tripplite.com at alioth-lists.debian.net> On Behalf Of Ken Olum Sent: Tuesday, January 14, 2020 11:24 AM To: Layne Fowler <layne.fowler at gmail.com> Cc: nut-upsuser at alioth-lists.debian.net Subject: [EXTERNAL] Re: [Nut-upsuser] Tripp Lite SMART1500LCD will not stay shut down when power is disconnected This is an EXTERNAL email. Please take a moment a...

On Dec 20, 2017, at 10:32 AM, Ken Olum wrote: > > 0.090564 find_nut_info: unknown info type: load.on.delay > 0.090577 find_nut_info: unknown info type: load.on.delay > 0.090585 Initiating UPS shutdown > 0.090593 upsdrv_shutdown... > 0.090601 instcmd(shutdown.return, [NULL]) > 0.090614 find_nut_info: unk...

On Jan 11, 2018, at 3:14 PM, Ken Olum wrote: > > So I monitored the USB port with wireshark (an interesting endeavor > since I didn't start out with any knowledge of USB protocols). But I > have managed to discover that when I ask Tripp Lite's poweralert > software to schedule a UPS shutdown, it does it by usin...

From: Charles Lepple <clepple at gmail.com> Date: Tue, 23 Jan 2018 09:02:14 -0500 On Jan 22, 2018, at 3:00 PM, Ken Olum <kdo at cosmos.phy.tufts.edu> wrote: > > I tested the effect of setting UPS.OutletSystem.Outlet.DelayBeforeShutdown > using Tripp Lite's software, which appears to be as follows: > Theoretically, this should be the same as running the command "upscmd bcpe...

On Mar 20, 2018, at 11:53 AM, Ken Olum <kdo at cosmos.phy.tufts.edu> wrote: > > Hi, Charles. Are you by any chance planning to address my problems > where NUT does not know how to schedule a shutdown of this Tripp-Lite > UPS? If not, could you point me in the right direction? My best > understanding of the situa...

[please use reply-all to post to the list - the mailing list does not add a reply-to header. thanks!] On Dec 18, 2017, at 11:37 AM, Ken Olum wrote: > > I have a Tripp-Lite BCPERS450, connected to a system running Ubuntu > 16.04.3 LTS and NUT 2.7.2-4ubuntu1.2. I had to make my own > /lib/systemd/system-shutdown/nutshutdown, but now everything is working > except for powering on and off the UPS. Regardless of the setting...

Thanks, Charles. I pulled your change and it fixed my segmentation fault. I discovered the following code at line 571 in usbhid-ups.c. This is part of the "checking for alternatives" code: if (!strcasecmp(cmdname, "shutdown.return")) { int ret; /* Ensure "ups.start.auto" is set to "yes", if supported */ if

...er information you need. On Tue, Jan 14, 2020 at 7:48 PM David Zomaya <David_Zomaya at tripplite.com> wrote: > Thanks Ken. > I'll plan to sit down and look up the protocol information over the next > week or so and follow up. > ------------------------------ > *From:* Ken Olum <kdo at cosmos.phy.tufts.edu> > *Sent:* Tuesday, January 14, 2020 1:35:10 PM > *To:* David Zomaya > *Cc:* kdo at cosmos.phy.tufts.edu; layne.fowler at gmail.com; > nut-upsuser at alioth-lists.debian.net > *Subject:* [EXTERNAL] Re: [Nut-upsuser] Tripp Lite SMART1500LCD will not...

From: Charles Lepple <clepple at gmail.com> Date: Thu, 11 Jan 2018 22:31:54 -0500 The trick will be adding support for this without breaking other models. For whatever it's worth, Tripp lite's software does not display the model number anywhere, so it may be treating all models the same. In case you are interested, this mapping between the "Path" and the

Hi, Charles. Are you by any chance planning to address my problems where NUT does not know how to schedule a shutdown of this Tripp-Lite UPS? If not, could you point me in the right direction? My best understanding of the situation of the moment is that the right control is UPS.OutletSystem.Outlet.DelayBeforeShutdown but that NUT does not know to use that. Thanks.

Thanks again for your help, Charles. I was able to install the Tripp Lite software on my Ubuntu machine, and it sort of works. It does something which continually changes the USB device ID of the UPS, and prints voluminous error messages in the log. However, one of the things that it can do is to schedule a UPS shutdown, which Nut does not know how to do. So I monitored the USB port with wireshark (an interesting endeavor since I didn't start out with any knowledge of USB protocols). But I have managed to...

When running 'sudo upsmon -c fsd' UPS turns off then back on after a delay as expected. But when power is disconnected and the command is ran, the UPS turns off but still turns back on again. Changing 'ondelay' to -1 or 0 does not change the behavior. How can I get the UPS load to stay turned off if there is no power? Or am I misunderstanding how to test this functionality?

Thanks for your help. From: Charles Lepple <clepple at gmail.com> Date: Mon, 18 Dec 2017 19:26:56 -0500 This may sound like an apples-to-oranges comparison, but we did uncover an issue with CyberPower UPSes where the delay values needed to be greater than or equal to 60 (seconds), since they were being rounded down to integer numbers of minutes internally: What was the largest

I have a Tripp-Lite BCPERS450, connected to a system running Ubuntu 16.04.3 LTS and NUT 2.7.2-4ubuntu1.2. I had to make my own /lib/systemd/system-shutdown/nutshutdown, but now everything is working except for powering on and off the UPS. Regardless of the settings of offdelay and ondelay in upsconf, and regardless of whether the AC power is on, when I say "upsdrvctl shutdown" the UPS

I tested the effect of setting UPS.OutletSystem.Outlet.DelayBeforeShutdown using Tripp Lite's software, which appears to be as follows: 1. If you set it when the line power is on, it turns off the UPS after the delay, and does not turn it back on again, even if you cycle the line power. 2. If you set it when the UPS is running on battery, wait for the UPS to turn off, and turn back on the