similar to: On the ups killpower via ethernet

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Hi to all, i install nut and it's work perfectly but when i start upsmon i recive the message: POWERDOWNFLAG (/etc/killpower) does not contain the upsmon magic string My upmon.conf contain: MONITOR myups@theseo 1 orion91 carlos81 master SHUTDOWNCMD "/sbin/shutdown -h +0" HOSTSYNC 15 POWERDOWNFLAG /etc/killpower FINALDELAY 5 My killpower scrit in /etc/killpower

On Jan 31, 2015, at 3:09 PM, Melvin Call <melvincall979 at gmail.com> wrote: > One last question if you don't mind. I noticed the "default" POWERDOWNFLAG is > set to /etc/killpower, but I changed that to /tmp and modified my umountroot > script to mount it read only too, because I know it gets wiped on reboot. Is > there anything that removes /etc/killpower on

On 1/31/15, Charles Lepple <clepple at gmail.com> wrote: > On Jan 31, 2015, at 3:09 PM, Melvin Call <melvincall979 at gmail.com> wrote: > >> One last question if you don't mind. I noticed the "default" POWERDOWNFLAG) >> is >> set to /etc/killpower, but I changed that to /tmp and modified my >> umountroot >> script to mount it read only

On Feb 1, 2015, at 7:04 AM, Melvin Call <melvincall979 at gmail.com> wrote: > Thank you Charles, for the assistance and the information. Everything is > completely functional here now. Not sure if the APC BackUPS ES550 is on the > list of compatible devices, but it works just fine with the usbhid-ups driver, > and supports several basic commands. You're welcome! We do have

Hello.... I'm testing the functionality of my NUT-setup (NUT 2.0.4-4 - Debian stable). The system is connected to the UPS, but is not powered by it. When running "upsmon -c fsd", upsmon says "Auto logout and shutdown proceeding". This is all well and good, but I never see the machine waiting for the UPS to cut the power. Instead it shuts down. It's my

Hello there I am new to NUT I am trying to monitor an APC smart-UPS with nut. I'd like to use the ethernet with SNMP (as opposed to serial port) because it's faster and it doesn't need to authenticate with user/pwd. The snmp-ups works with our APC, however I noticed a significant problem: If snmp-ups is started when the UPS is not reachable (e.g. we have a slow switch that drops

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Hi Everyone, I recently bought a Tripp-Lite SMART1500LCD for my Linux Mint 19.3 machine, connected via a USB cable. I installed Nut 2.7.4 from the Mint package repository via sudo apt update && sudo apt install nut. Everything works great: NUT issues low battery warning when it reaches the set low battery point and then issues shutdown commands...computer shuts down..then the UPS shuts

This information will be mirrored on the Xen 4.4 Roadmap wiki page: http://wiki.xen.org/wiki/Xen_Roadmap/4.4 Our timeline had us start the code freeze last Friday. However, we have not released an RC0 because we have been waiting for PVH dom0 support. Adding bug fixes during RCs makes sense, but RC0 should contain all of the functionality we expect to be in the final release. PVH dom0 support

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A few months back, I tried to use the network scripts to provision an IPv6 range like can be done with IPv4. I was using CentOS 5.2 at the time and was informed that 5.2 was broken in this regard. I have upgraded to CentOS 5.3 now and I am trying to get IPv6 to provision an entire range of IPs, but I am still getting the old behavior and no IPs are

After 3.10 you'd need to use storhaug.... Which.... doesn't work (yet). You need to use 3.10 for now. On 07/06/2017 12:53 PM, Anthony Valentine wrote: > I'm running this on CentOS 7.3 > > [root at glustertest1 ~]# cat /etc/redhat-release > CentOS Linux release 7.3.1611 (Core) > > > Here are the software versions I have installed. > > [root at

02:00.0 VGA compatible controller: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] (rev a1) Chipset: G98 (NV98) Family : NV50 The same for all four kernel: - 3.18.0-0.rc0.git8.1.fc22.x86_64 - 3.18.0-0.rc0.git9.1.fc22.x86_64 - 3.18.0-0.rc0.git9.3.fc22.x86_64 - 3.18.0-0.rc0.git9.4.fc22.x86_64 after "fb: switching to nouveaufb from VESA VGA" display is powered off. The magic SysRq key

I have an MGE UPS Pulsar Ellipse 600 USBS that I'm setting up with CentOS 4.4 I tried for some time to get it working with USB, but failed and I have had much more success using the serial port. I have managed to complete the whole install procedure (shown here: http://www.networkupstools.org/doc/2.0.1/INSTALL.html )but I'm lost when it comes to implementing the shutdown script. I'm

On 20.10.2014 08:13, poma wrote: > > 02:00.0 VGA compatible controller: > NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] (rev a1) > Chipset: G98 (NV98) > Family : NV50 > > The same for all four kernel: > - 3.18.0-0.rc0.git8.1.fc22.x86_64 > - 3.18.0-0.rc0.git9.1.fc22.x86_64 > - 3.18.0-0.rc0.git9.3.fc22.x86_64 > - 3.18.0-0.rc0.git9.4.fc22.x86_64 > after >

Does anyone have any experience getting LIRC 0.9.0 up and running on CentOS 6.6? I have the packages from EPEL installed: lirc.x86_64 0.9.0-8.el6 @epel lirc-doc.x86_64 0.9.0-8.el6 @epel lirc-libs.x86_64 0.9.0-8.el6 @epel lirc-remotes.x86_64 0.9.0-8.el6 @epel And my IR

On 21.10.2014 02:23, poma wrote: > On 20.10.2014 21:30, poma wrote: >> On 20.10.2014 08:13, poma wrote: >>> >>> 02:00.0 VGA compatible controller: >>> NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] (rev a1) >>> Chipset: G98 (NV98) >>> Family : NV50 >>> >>> The same for all four kernel: >>> -

Dear Poma, Don't get anyone wrong, your input is greatly valued. The reason why "we" (nouveau developers) generally ask for a git bisection is because we don't know or track specific distributions. Although your search has narrowed the problem down (thanks for that!), we don't know how big the difference is between kernel-3.16.0-0.rc0.git9.1.fc21 and

On 20.10.2014 21:30, poma wrote: > On 20.10.2014 08:13, poma wrote: >> >> 02:00.0 VGA compatible controller: >> NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] (rev a1) >> Chipset: G98 (NV98) >> Family : NV50 >> >> The same for all four kernel: >> - 3.18.0-0.rc0.git8.1.fc22.x86_64 >> - 3.18.0-0.rc0.git9.1.fc22.x86_64 >> -

On Mon, 23 Mar 2015 10:36:33 -0400 John Snow <jsnow@redhat.com> wrote: > > Are the needed patches in 2.3.0-rc0? > > Is it possible to backport AHCI migration to RHEL 7.1 qemu or will it be too much work? > > The patches that improve the stability of AHCI migration are in 2.3-rc0. > We still have not /enabled/ migration upstream, but editing to code to > allow it