On 17 Jun 2002, David Dyer-Bennet wrote: > I finally started trying to hook my two Linux servers up to my two APC > Back-ups UPSs last night (one's a 600, one's a 650). I had monitoring > and shutdown working back in the old house with the old UPS and a > different version of Linux. I'd forgotten how annoying the cabling > issues are. Ick. And I don't want to pay $40 each for cables, and I > don't *especially* want to run their Powerchute software, either. > > Note that my two UPSs use "stupid" communications protocol, not > "smart". There's actually a diagram in the Back-ups 600 manual > showing what each connection on the 9-pin port is (I believe from > reading how-tos and things that they 600 and 650 are about the same in > this; the 650 manual doesn't actually give a diagram, though). I can't vouch for the serial cable wiring, but you might want the package apcupsd: --- snip --- Packager : Kern Sibbald <kern at sibbald.com> URL : http://www.sibbald.com/apcupsd/ Summary : APC UPS Power Control Daemon for Linux Description : Apcupsd can be used for controlling most APC UPSes. During a power failure, apcupsd will inform the users about the power failure and that a shutdown may occur. If power is not restored, a system shutdown will follow when the battery is exausted, a timeout (seconds) expires, or the battery runtime expires based on internal APC calculations determined by power consumption rates. If the power is restored before one of the above shutdown conditions is met, apcupsd will inform users about this fact. Some features depend on what UPS model you have (simple or smart). --- snip --- I can say for sure that it's talking to my UPS: --- snip --- Broadcast message from root Mon Jun 17 15:26:17 2002... Power failure on UPS APC1400. Running on batteries. Broadcast message from root Mon Jun 17 15:29:55 2002... Power has returned on UPS APC1400... --- snip --- (Yes, today. Amazing coincidence. We were just rewiring the server room.) I can't tell you for sure if the shutdown feature works; we've yet to have an outage that long here (and it's a production environment, so no testing...maybe on the next one?). Hope that provides some sort of insight. Jima