Nabble - Apcupsd UPS control software

tag:www.nabble.com,2006:forum-3705 Nabble - Apcupsd UPS control software 2008-10-07T13:27:37Z Apcupsd is a program for monitoring UPSes and performing a graceful computer shutdown in the event of a power failure. It runs on Linux, Tru64, Mac OS/X, Win32, Solaris as well as other OSes. It can deliver the UPS status via the network to any brows Apcupsd UPS control software home is <a href="http://sourceforge.net/projects/apcupsd/" target="_top" rel="nofollow">here</a>. tag:www.nabble.com,2006:post-19866569 Re: apcupsd FATAL ERROR in ../drivers/pcnet/pcnet.c at line 655 2008-10-07T13:27:37Z 2008-10-07T13:27:37Z Joseph L. Casale >I receive the above error when trying to stop and restart the APCUPSD service <br>after making a change to the configuration file. <br><br>Ok. <br><br>>I receive this error and I must uninstall, reboot then reinstall. <br><br>Heh, did you try to revert the change and restart the service? <br><br>I am guessing you simply have a config error and the daemon can't <br>cope with it. The resolution will be hard to come about w/o seeing <br>your config:) Post some info... <br><br>jlc <br><br><br>------------------------------------------------------------------------- <br>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge <br>Build the coolest Linux based applications with Moblin SDK & win great prizes <br>Grand prize is a trip for two to an Open Source event anywhere in the world <br><a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/" target="_top" rel="nofollow">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a><br>_______________________________________________ <br>Apcupsd-users mailing list <br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19866569&i=0" target="_top" rel="nofollow">Apcupsd-users@...</a> <br><a href="https://lists.sourceforge.net/lists/listinfo/apcupsd-users" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a><br><p>From forum: <a href="http://www.nabble.com/apcupsd-users-f3707.html" embed="fixTarget[3707]" target="_top" >apcupsd-users</a></p> tag:www.nabble.com,2006:post-19866062 apcupsd FATAL ERROR in ../drivers/pcnet/pcnet.c at line 655 2008-10-07T12:42:30Z 2008-10-07T12:42:30Z NFritsch I receive the above error when trying to stop and restart the APCUPSD service <br>after making a change to the configuration file.  I receive this error and I <br>must uninstall, reboot then reinstall.  Does anyone have a resolution or a <br>tip on how to avoid this?  I'm using the pcnet driver to connect to a <br>Smart-UPS 8000 via IP address.  Thanks. <br>***************************************************** <br>Nicholas R. Fritsch <br>Keating Muething & Klekamp PLL <br>One East Fourth Street <br>Suite 1400 <br>Cincinnati, OH  45202 <br>Tel: 513-562-1424 <br>Fax: 513-579-6457 <br>Internet Address: <a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19866062&i=0" target="_top" rel="nofollow">nfritsch@...</a> <br>Website: www.kmklaw.com <br><br>            --- CONFIDENTIALITY STATEMENT --- <br>This e-mail transmission contains information that is <br>intended to be privileged and confidential.  It is in- <br>tended only for the addressee named above.  If you re- <br>ceive this e-mail in error, please do not read, copy <br>or disseminate it in any manner.  If you are not the <br>intended recipient, any disclosure, copying, distri- <br>bution or use of the contents of this information is <br>prohibited.  Please reply to the message immediately by <br>informing the sender that the message was misdirected. <br>After replying, please erase it from your computer <br>system.  Your assistance in correcting this error is <br>appreciated. <br>****************************************************** <br><br>------------------------------------------------------------------------- <br>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge <br>Build the coolest Linux based applications with Moblin SDK & win great prizes <br>Grand prize is a trip for two to an Open Source event anywhere in the world <br><a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/" target="_top" rel="nofollow">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a><br>_______________________________________________ <br>Apcupsd-users mailing list <br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19866062&i=1" target="_top" rel="nofollow">Apcupsd-users@...</a> <br><a href="https://lists.sourceforge.net/lists/listinfo/apcupsd-users" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a><br><p>From forum: <a href="http://www.nabble.com/apcupsd-users-f3707.html" embed="fixTarget[3707]" target="_top" >apcupsd-users</a></p> tag:www.nabble.com,2006:post-19842341 Re: APCUPSD Manual ( was BAT with older director) 2008-10-06T09:49:32Z 2008-10-06T09:49:32Z Steve Garcia Joseph L. Casale wrote: <br>>> Any advice to get a working manual for the version I have? <br>> <br>> <a href="http://www.apcupsd.org/" target="_top" rel="nofollow">http://www.apcupsd.org/</a><br>> <br>> Look on the left :) <br><br>Well, the website has the most current manual.  I looked all over for a <br>manual that goes with 3.12.4, but couldn't find it. <br><br>Still can't. <br><br>But I gave up on trying to get the Debian furnished doc files to build <br>and downloaded the 3.12.4 source and built the manual from that. <br><br><br>-- <br>Steve Garcia <br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19842341&i=0" target="_top" rel="nofollow">sgarcia@...</a> <br>Ignorance killed the cat; Curiosity was framed. <br><br>------------------------------------------------------------------------- <br>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge <br>Build the coolest Linux based applications with Moblin SDK & win great prizes <br>Grand prize is a trip for two to an Open Source event anywhere in the world <br><a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/" target="_top" rel="nofollow">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a><br>_______________________________________________ <br>Apcupsd-users mailing list <br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19842341&i=1" target="_top" rel="nofollow">Apcupsd-users@...</a> <br><a href="https://lists.sourceforge.net/lists/listinfo/apcupsd-users" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a><br><p>From forum: <a href="http://www.nabble.com/apcupsd-users-f3707.html" embed="fixTarget[3707]" target="_top" >apcupsd-users</a></p> tag:www.nabble.com,2006:post-19838742 Re: USB Interface on NetBSD 2008-10-06T07:07:25Z 2008-10-06T07:07:25Z Adam Kropelin On Thu, Oct 2, 2008 at 2:55 PM, Alfonso Elefante <<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19838742&i=0" target="_top" rel="nofollow">alfoele@...</a>> wrote: <div class='shrinkable-quote'><br>> I recently bought an APC UPS (Back-UPS ES 700, with USB Interface) to <br>> protect my Soekris NET5501 system running Netbsd 4.0. Before installing <br>> apcupsd on Netbsd, I recompiled the kernel to force ugen device detection <br>> (as explained in apcupsd manual), but: <br>> <br>> - if I plug the USB cable into the NET5501 system after it has booted, the <br>> UPS is correctly detected by the system (as ugen0) and apcupsd runs and is <br>> connected to the UPS; <br>> - if I boot the system (both hot/cold reboot) with the UPS USB cable already <br>> plugged-in, the system doesn't detect the UPS and apcupsd start fails. If I <br>> unplug and replug the USB cable into the system, it correctly sees the UPS <br>> and, after restarting apcupsd, it works again. <br>> <br>> Do someone have a solution or any suggestion? </div><br>This appears to be a NetBSD kernel issue where it does not recognize <br>that a device is already plugged it. I think you will be more likely <br>to get an answer if you ask on a NetBSD mailing list. <br><br>--Adam <br><br>------------------------------------------------------------------------- <br>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge <br>Build the coolest Linux based applications with Moblin SDK & win great prizes <br>Grand prize is a trip for two to an Open Source event anywhere in the world <br><a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/" target="_top" rel="nofollow">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a><br>_______________________________________________ <br>Apcupsd-users mailing list <br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19838742&i=1" target="_top" rel="nofollow">Apcupsd-users@...</a> <br><a href="https://lists.sourceforge.net/lists/listinfo/apcupsd-users" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a><br><p>From forum: <a href="http://www.nabble.com/apcupsd-users-f3707.html" embed="fixTarget[3707]" target="_top" >apcupsd-users</a></p> tag:www.nabble.com,2006:post-19838950 Re: Compatibility with very old smart-ups'es (SU600I, SU2000I) 2008-10-06T07:06:14Z 2008-10-06T07:06:14Z Adam Kropelin On Fri, Oct 3, 2008 at 3:41 AM, Michal Soltys <<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19838950&i=0" target="_top" rel="nofollow">soltys@...</a>> wrote: <br>> I have a few very old upses (models as mentioned in subject) - some of <br>> them work fine with apcupsd/apctest, whereas some others don't react to <br>> 'a' command, causing both apctest and apcupsd to wait indefinitely for <br>> its results. <br>> <br>> Is there any way / workaround to get them working under apcupsd control ? <br><br>apcupsd waits something like 30 seconds for a response to the 'a' <br>command, then falls back on probing. It does not wait indefinitely. <br>apctest should do the same, although I haven't specifically tried it <br>lately. Are you running a modern version of apcupsd (3.12.x or <br>higher)? <br><br>--Adam <br><br>------------------------------------------------------------------------- <br>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge <br>Build the coolest Linux based applications with Moblin SDK & win great prizes <br>Grand prize is a trip for two to an Open Source event anywhere in the world <br><a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/" target="_top" rel="nofollow">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a><br>_______________________________________________ <br>Apcupsd-users mailing list <br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19838950&i=1" target="_top" rel="nofollow">Apcupsd-users@...</a> <br><a href="https://lists.sourceforge.net/lists/listinfo/apcupsd-users" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a><br><p>From forum: <a href="http://www.nabble.com/apcupsd-users-f3707.html" embed="fixTarget[3707]" target="_top" >apcupsd-users</a></p> tag:www.nabble.com,2006:post-19838662 Re: cannot allocate memory 2008-10-06T07:02:53Z 2008-10-06T07:02:53Z Adam Kropelin On Mon, Sep 22, 2008 at 11:00 AM, Robert A Wooldridge <br><<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19838662&i=0" target="_top" rel="nofollow">bob.wooldridge@...</a>> wrote: <div class='shrinkable-quote'><br>> I have apcupsd installed on my mail server.  I'm running Debian lenny and I <br>> used the apcupsd package from there.  It is version 3.14.4.  I am connected <br>> to a 1500xlm with a network card configured.  I am using the power chute <br>> setting.  When I start apcupsd, I get this error message: <br>> Unable to start thread: ERR=Cannot allocate memory <br>> <br>> However, apcupsd is still running and it continues to log events.  So what <br>> does this error refer to? <br>> <br>> <br>> I am also not able to do apcaccess status.  When I do this I get: <br>> Error contacting apcupsd @ localhost:3551: Connection refused <br>> <br>> Is this supposed to work when using pcnet configuration? </div><br>The two issues are related. The error message indicates that apcupsd <br>was unable to start the NIS thread which responds to apcaccess <br>requests. Without that thread running, apcaccess will not work. <br><br>I'd guess either you have memory overcommit support disabled and are <br>running very low on memory or there is some security component such as <br>SELinux getting in the way, preventing apcupsd from spawning a thread. <br><br>--Adam <br><br>------------------------------------------------------------------------- <br>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge <br>Build the coolest Linux based applications with Moblin SDK & win great prizes <br>Grand prize is a trip for two to an Open Source event anywhere in the world <br><a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/" target="_top" rel="nofollow">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a><br>_______________________________________________ <br>Apcupsd-users mailing list <br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19838662&i=1" target="_top" rel="nofollow">Apcupsd-users@...</a> <br><a href="https://lists.sourceforge.net/lists/listinfo/apcupsd-users" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a><br><p>From forum: <a href="http://www.nabble.com/apcupsd-users-f3707.html" embed="fixTarget[3707]" target="_top" >apcupsd-users</a></p> tag:www.nabble.com,2006:post-19834930 Re: Bug: in code for BackUps-Pro and 940-0095B cable 2008-10-06T02:10:53Z 2008-10-06T02:10:53Z Trevor Roydhouse David C. Rankin wrote: <div class='shrinkable-quote'><br>>> 10:17 nemesis~> nocomment /etc/apcupsd/apcupsd.conf <br>>> UPSNAME Nemesis <br>>> UPSCABLE 940-0095A <br>>> UPSTYPE apcsmart <br>>> DEVICE /dev/ttyS0 <br>>> LOCKFILE /var/lock <br>>> SCRIPTDIR /etc/apcupsd <br>>> PWRFAILDIR /etc/apcupsd <br>>> NOLOGINDIR /etc <br>>> ONBATTERYDELAY 6 <br>>> BATTERYLEVEL 5 <br>>> MINUTES 3 <br>>> TIMEOUT 0 <br>>> ANNOY 300 <br>>> ANNOYDELAY 60 <br>>> NOLOGON disable <br>>> KILLDELAY 0 <br>>> NETSERVER on <br>>> NISIP 0.0.0.0 <br>>> NISPORT 3551 <br>>> EVENTSFILE /var/log/apcupsd.events <br>>> EVENTSFILEMAX 10 <br>>> UPSCLASS standalone <br>>> UPSMODE disable <br>>> STATTIME 0 <br>>> STATFILE /var/log/apcupsd.status <br>>> LOGSTATS off <br>>> DATATIME 0 <br>>> BATTDATE 08/15/08 </div>[CHOMP] <div class='shrinkable-quote'><br>>> Full output from apcaccess being (this <br>>> output is from unit 1 with the 940-0095a cable): <br>>> <br>>> 10:17 nemesis~> apcaccess status <br>>> APC      : 001,050,1238 <br>>> DATE     : Mon Sep 15 10:16:37 CDT 2008 <br>>> HOSTNAME : nemesis <br>>> RELEASE  : 3.14.3 <br>>> VERSION  : 3.14.3 (20 January 2008) suse <br>>> UPSNAME  : Nemesis <br>>> CABLE    : APC Cable 940-0095A <br>>> MODEL    : BACK-UPS PRO 650 <br>>> UPSMODE  : Stand Alone <br>>> STARTTIME: Mon Sep 15 07:32:18 CDT 2008 <br>>> STATUS   : ONLINE <br>>> LINEV    : 118.8 Volts <br>>> LOADPCT  :  24.7 Percent Load Capacity <br>>> BCHARGE  : 100.0 Percent <br>>> TIMELEFT :   5.0 Minutes <br>>> MBATTCHG : 5 Percent <br>>> MINTIMEL : 3 Minutes <br>>> MAXTIME  : 0 Seconds <br>>> MAXLINEV : 118.8 Volts <br>>> MINLINEV : 118.0 Volts <br>>> OUTPUTV  : 118.0 Volts <br>>> SENSE    : High <br>>> DWAKE    : 000 Seconds <br>>> DSHUTD   : 020 Seconds <br>>> DLOWBATT : 02 Minutes <br>>> LOTRANS  : 106.0 Volts <br>>> HITRANS  : 127.0 Volts <br>>> RETPCT   : 000.0 Percent <br>>> ALARMDEL : 5 seconds <br>>> BATTV    : 14.1 Volts <br>>> LINEFREQ : 60.0 Hz <br>>> LASTXFER : Line voltage notch or spike <br>>> NUMXFERS : 4 <br>>> XONBATT  : Mon Sep 15 10:09:24 CDT 2008 <br>>> TONBATT  : 0 seconds <br>>> CUMONBATT: 4 seconds <br>>> XOFFBATT : Mon Sep 15 10:09:25 CDT 2008 <br>>> SELFTEST : NO <br>>> STESTI   : 336 <br>>> STATFLAG : 0x07000008 Status Flag <br>>> REG1     : 0x00 Register 1 <br>>> REG2     : 0x00 Register 2 <br>>> REG3     : 0x00 Register 3 <br>>> MANDATE  : 05/23/99 <br>>> SERIALNO : NB9921121779 <br>>> BATTDATE : 08/15/08 <br>>> NOMOUTV  : 115 Volts <br>>> NOMBATTV :  12.0 Volts <br>>> FIRMWARE : 12.3.D <br>>> APCMODEL : CWD <br>>> END APC  : Mon Sep 15 10:17:22 CDT 2008 </div>[CHOMP] <br><br>Hmmmm. My trusty Backup Pro 650 (PNP) using the APC cable 940-0095A <br>supplied with the unit (the same report is generated with the APC cable <br>940-0024C and the homemade smart cable) reports only: <br><br>APC      : 001,025,0648 <br>DATE     : Mon Oct 06 19:56:28 EST 2008 <br>HOSTNAME : shadow.sentry.org <br>RELEASE  : 3.14.4 <br>VERSION  : 3.14.4 (18 May 2008) freebsd <br>UPSNAME  : SHADOW <br>CABLE    : APC Cable 940-0095A <br>MODEL    : BACK-UPS PRO  650 <br>UPSMODE  : Stand Alone <br>STARTTIME: Mon Oct 06 19:56:22 EST 2008 <br>STATUS   : ONLINE <br>MBATTCHG : -1 Percent <br>MINTIMEL : 5 Minutes <br>MAXTIME  : 0 Seconds <br>LASTXFER : Automatic or explicit self test <br>NUMXFERS : 0 <br>TONBATT  : 0 seconds <br>CUMONBATT: 0 seconds <br>XOFFBATT : N/A <br>SELFTEST : NO <br>STATFLAG : 0x07000008 Status Flag <br>REG1     : 0x00 Register 1 <br>REG3     : 0x00 Register 3 <br>SERIALNO : GB9819548669 <br>FIRMWARE : 61.L.I (61 = Australia, L = ?, I = International version) <br>END APC  : Mon Oct 06 19:56:34 EST 2008 <br><br>... and apctest reports capabilities in line with this (hmmm, the NA is <br>missing when there's no result, Adam?): <br><br>===================== <br>Simulating UPSlinkCheck ... <br>Wrote: Y Got: SM <br>Attempting to use smart_poll() ... <br>Sent: Y Got: SM  Good -- smart_poll() works!. <br><br>Going to ask for valid commands... <br>Protocol version is: 2) <br>Alert characters are: ?=*%+#!$ <br>Command characters are: 98~`^Aynba@YXUSQKGA^M <br><br>Now running through apcupsd get_UPS capabilities(). <br>NA  indicates that the feature is Not Available <br><br>UPS Status: 08 <br>Line quality: FF <br>Reason for last transfer to batteries: T <br>Self-Test Status: OK <br>Line Voltage: <br>Line Voltage Max: <br>Line Voltage Min: <br>Output Voltage: <br>Batt level percent: <br>Batt voltage: <br>UPS Load: <br>Line freq: <br>Runtime left: <br>UPS Internal temp: <br>Dip switch settings: <br>Register 1: 00 <br>Register 2: 00 <br>Register 3: 00 <br>Sensitivity: <br>Wakeup delay: <br>Sleep delay: <br>Low transfer voltage: <br>High transfer voltage: <br>Batt charge for return: <br>Alarm status: <br>Low battery shutdown level: <br>UPS Name: <br>UPS Self test interval: <br>UPS manufacture date: <br>UPS serial number: GB9819548669 <br>Date battery replaced: <br>Output voltage when on batteries: <br>Nominal battery voltage: <br>Percent humidity: <br>Ambient temperature: <br>Firmware revision: 61.L.I <br>Number of external batteries installed: <br>Number of bad batteries installed: <br>UPS model as defined by UPS: <br>UPS EPROM capabilities string: <br>The EPROM string is 0 characters long! <br>Hours since last self test: <br><br>That is all for now. <br>===================== <br><br>All of which tends to suggest that there are various firmware and <br>protocol differences within the same model which affect capabilities and <br>not just cable types or apcupsd code. (I also get identical results from <br>a BackUPS Pro 1400.) <br><br>I guess my point is that I wonder whether you're certain that the <br>940-0095B cable and your BackUPS Pro 650 did provide produce the same <br>information as your 940-0095A example above. <br><br>-- <br>Trevor Roydhouse                            Mob  : 0415-448-273 <br>BJuris, LLB, LLM (UNSW) <br>System Developer <br>Australasian Legal Information Institute    Web  : www.austlii.edu.au <br><br>------------------------------------------------------------------------- <br>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge <br>Build the coolest Linux based applications with Moblin SDK & win great prizes <br>Grand prize is a trip for two to an Open Source event anywhere in the world <br><a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/" target="_top" rel="nofollow">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a><br>_______________________________________________ <br>Apcupsd-users mailing list <br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19834930&i=0" target="_top" rel="nofollow">Apcupsd-users@...</a> <br><a href="https://lists.sourceforge.net/lists/listinfo/apcupsd-users" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a><br><p>From forum: <a href="http://www.nabble.com/apcupsd-users-f3707.html" embed="fixTarget[3707]" target="_top" >apcupsd-users</a></p> tag:www.nabble.com,2006:post-19831519 Re: Bug: in code for BackUps-Pro and 940-0095B cable 2008-10-05T20:00:46Z 2008-10-05T20:00:46Z David C. Rankin David C. Rankin wrote: <div class='shrinkable-quote'><br>> Listmates, Developers: <br>> <br>> There is a lingering problem with the code for the apcsmart <br>> (backupspropnp|newbackupspropnp) UPSTYPE for the APC backups pro models. I have <br>> used apcupsd with two of these same bps650 units since May 2000. The problem is <br>> with the output now available with the 940-0095b cable does not correctly <br>> provide all parameters from the ups. The systems, (1) and (2) (both with <br>> backups pro 650 models) are as follows: <br>> <br>> (1) openSuSE 11.0; Linux nemesis 2.6.25.16-0.1-pae #1 SMP 2008-08-21 00:34:25 <br>> +0200 i686 athlon i386 GNU/Linux: <br>> <br>> 10:17 nemesis~> nocomment /etc/apcupsd/apcupsd.conf <br>> UPSNAME Nemesis <br>> UPSCABLE 940-0095A <br>> UPSTYPE apcsmart <br>> DEVICE /dev/ttyS0 <br>> LOCKFILE /var/lock <br>> SCRIPTDIR /etc/apcupsd <br>> PWRFAILDIR /etc/apcupsd <br>> NOLOGINDIR /etc <br>> ONBATTERYDELAY 6 <br>> BATTERYLEVEL 5 <br>> MINUTES 3 <br>> TIMEOUT 0 <br>> ANNOY 300 <br>> ANNOYDELAY 60 <br>> NOLOGON disable <br>> KILLDELAY 0 <br>> NETSERVER on <br>> NISIP 0.0.0.0 <br>> NISPORT 3551 <br>> EVENTSFILE /var/log/apcupsd.events <br>> EVENTSFILEMAX 10 <br>> UPSCLASS standalone <br>> UPSMODE disable <br>> STATTIME 0 <br>> STATFILE /var/log/apcupsd.status <br>> LOGSTATS off <br>> DATATIME 0 <br>> BATTDATE 08/15/08 <br>> <br>> (2) openSuSE 10.3; Linux bonza 2.6.22.18-0.2-default #1 SMP 2008-06-09 13:53:20 <br>> +0200 i686 athlon i386 GNU/Linux <br>> <br>> 10:15 bonza~> nocomment /etc/apcupsd/apcupsd.conf <br>> UPSCABLE 940-0095B <br>> UPSTYPE apcsmart <br>> DEVICE /dev/ttyS1 <br>> LOCKFILE /var/lock <br>> SCRIPTDIR /etc/apcupsd <br>> PWRFAILDIR /etc/apcupsd <br>> NOLOGINDIR /etc <br>> ONBATTERYDELAY 6 <br>> BATTERYLEVEL 5 <br>> MINUTES 3 <br>> TIMEOUT 0 <br>> ANNOY 300 <br>> ANNOYDELAY 60 <br>> NOLOGON disable <br>> KILLDELAY 0 <br>> NETSERVER on <br>> NISIP 0.0.0.0 <br>> NISPORT 3551 <br>> EVENTSFILE /var/log/apcupsd.events <br>> EVENTSFILEMAX 10 <br>> UPSCLASS standalone <br>> UPSMODE disable <br>> STATTIME 0 <br>> STATFILE /var/log/apcupsd.status <br>> LOGSTATS off <br>> DATATIME 0 <br>> <br>> The problem: For years (guessing 2000 - 2005) unit 2 above (bonza) gave full <br>> output with the 940-0095b cable and UPSTYPE backupspropnp, now nothing but <br>> simple signaling output is available. Full output from apcaccess being (this <br>> output is from unit 1 with the 940-0095a cable): <br>> <br>> 10:17 nemesis~> apcaccess status <br>> APC      : 001,050,1238 <br>> DATE     : Mon Sep 15 10:16:37 CDT 2008 <br>> HOSTNAME : nemesis <br>> RELEASE  : 3.14.3 <br>> VERSION  : 3.14.3 (20 January 2008) suse <br>> UPSNAME  : Nemesis <br>> CABLE    : APC Cable 940-0095A <br>> MODEL    : BACK-UPS PRO 650 <br>> UPSMODE  : Stand Alone <br>> STARTTIME: Mon Sep 15 07:32:18 CDT 2008 <br>> STATUS   : ONLINE <br>> LINEV    : 118.8 Volts <br>> LOADPCT  :  24.7 Percent Load Capacity <br>> BCHARGE  : 100.0 Percent <br>> TIMELEFT :   5.0 Minutes <br>> MBATTCHG : 5 Percent <br>> MINTIMEL : 3 Minutes <br>> MAXTIME  : 0 Seconds <br>> MAXLINEV : 118.8 Volts <br>> MINLINEV : 118.0 Volts <br>> OUTPUTV  : 118.0 Volts <br>> SENSE    : High <br>> DWAKE    : 000 Seconds <br>> DSHUTD   : 020 Seconds <br>> DLOWBATT : 02 Minutes <br>> LOTRANS  : 106.0 Volts <br>> HITRANS  : 127.0 Volts <br>> RETPCT   : 000.0 Percent <br>> ALARMDEL : 5 seconds <br>> BATTV    : 14.1 Volts <br>> LINEFREQ : 60.0 Hz <br>> LASTXFER : Line voltage notch or spike <br>> NUMXFERS : 4 <br>> XONBATT  : Mon Sep 15 10:09:24 CDT 2008 <br>> TONBATT  : 0 seconds <br>> CUMONBATT: 4 seconds <br>> XOFFBATT : Mon Sep 15 10:09:25 CDT 2008 <br>> SELFTEST : NO <br>> STESTI   : 336 <br>> STATFLAG : 0x07000008 Status Flag <br>> REG1     : 0x00 Register 1 <br>> REG2     : 0x00 Register 2 <br>> REG3     : 0x00 Register 3 <br>> MANDATE  : 05/23/99 <br>> SERIALNO : NB9921121779 <br>> BATTDATE : 08/15/08 <br>> NOMOUTV  : 115 Volts <br>> NOMBATTV :  12.0 Volts <br>> FIRMWARE : 12.3.D <br>> APCMODEL : CWD <br>> END APC  : Mon Sep 15 10:17:22 CDT 2008 <br>> <br>> Now with the 940-0095b cable, regardless of the UPSTYPE used, all that is <br>> available with apcaccess is: <br>> <br>> 10:15 bonza~> apcaccess status <br>> APC      : 001,019,0476 <br>> DATE     : Sun Sep 14 22:37:18 CDT 2008 <br>> HOSTNAME : bonza <br>> RELEASE  : 3.14.4 <br>> VERSION  : 3.14.4 (18 May 2008) suse <br>> UPSNAME  : bonza <br>> CABLE    : APC Cable 940-0095B <br>> MODEL    : DUMB UPS Driver <br>> UPSMODE  : Stand Alone <br>> STARTTIME: Sat Sep 13 21:30:37 CDT 2008 <br>> STATUS   : ONLINE <br>> MBATTCHG : 5 Percent <br>> MINTIMEL : 3 Minutes <br>> MAXTIME  : 0 Seconds <br>> NUMXFERS : 0 <br>> TONBATT  : 0 seconds <br>> CUMONBATT: 0 seconds <br>> XOFFBATT : N/A <br>> STATFLAG : 0x07000008 Status Flag <br>> END APC  : Mon Sep 15 10:15:52 CDT 2008 <br>> <br>> That is wrong and that is where the bug is. This box (bonza) with the <br>> 940-0095b cable used to provide the full output shown above for (nemesis with <br>> the 940-0095a cable). From my best recollection, this bug appeared when the old <br>> UPSTYPE of backupspropnp was incorporated into the catchall apcsmart type. (I <br>> know that was years ago). Notwithstanding, I would like to be able to get full <br>> output from the 940-0095b cable back. I know it will do it, I saw it with <br>> apcupsd for 5 years, then it disappeared. <br>> <br>> Please take a look at the code. Somewhere the 940-0095b cable is not being <br>> handled correctly and the functionality is degraded. From the apcaccess output <br>> the problem appears to be that even with UPSTYPE apcsmart the 940-0095b cable <br>> causes the MODEL to revert to "DUMB UPS Driver". These ups'es are not dumb and <br>> the 940-0095b cable used to provide a perfect "smart" interface to them, but no <br>> longer does. <br>> <br>> As always, if I can provide you with more information or do additional <br>> testing, just let me know. I'm more than happy to do my part and help. <br>> <br>> Thanks. <br>> </div><br>Listmates, <br><br>        I thought I would follow-up and provide my apcupsd.conf as suggested. The file <br>from an openSuSE 10.3 - i586 install is: <br><br>21:54 bonza~> nocomment /etc/apcupsd/apcupsd.conf <br>UPSCABLE 940-0095B <br>UPSTYPE apcsmart <br>DEVICE /dev/ttyS1 <br>LOCKFILE /var/lock <br>SCRIPTDIR /etc/apcupsd <br>PWRFAILDIR /etc/apcupsd <br>NOLOGINDIR /etc <br>ONBATTERYDELAY 6 <br>BATTERYLEVEL 5 <br>MINUTES 3 <br>TIMEOUT 0 <br>ANNOY 300 <br>ANNOYDELAY 60 <br>NOLOGON disable <br>KILLDELAY 0 <br>NETSERVER on <br>NISIP 0.0.0.0 <br>NISPORT 3551 <br>EVENTSFILE /var/log/apcupsd.events <br>EVENTSFILEMAX 10 <br>UPSCLASS standalone <br>UPSMODE disable <br>STATTIME 0 <br>STATFILE /var/log/apcupsd.status <br>LOGSTATS off <br>DATATIME 0 <br><br>        I do hope that someone can take a look at this issues and hopefully find out <br>where the problem is. I do not have a config.out file as this was from an rpm <br>install. If you would like, I can download the .src.rpm and get the information <br>that way. However, the issue seems to be in the handling of the 940-0095B cable <br>and not with any ./configure issue. If I can provide anything else, just let me <br>know. Thanks. <br><br>-- <br>David C. Rankin, J.D., P.E. <br>Rankin Law Firm, PLLC <br>510 Ochiltree Street <br>Nacogdoches, Texas 75961 <br>Telephone: (936) 715-9333 <br>Facsimile: (936) 715-9339 <br>www.rankinlawfirm.com <br><br>------------------------------------------------------------------------- <br>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge <br>Build the coolest Linux based applications with Moblin SDK & win great prizes <br>Grand prize is a trip for two to an Open Source event anywhere in the world <br><a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/" target="_top" rel="nofollow">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a><br>_______________________________________________ <br>Apcupsd-users mailing list <br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19831519&i=0" target="_top" rel="nofollow">Apcupsd-users@...</a> <br><a href="https://lists.sourceforge.net/lists/listinfo/apcupsd-users" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a><br><p>From forum: <a href="http://www.nabble.com/apcupsd-users-f3707.html" embed="fixTarget[3707]" target="_top" >apcupsd-users</a></p> tag:www.nabble.com,2006:post-19830295 Re: Back-UPS HS? 2008-10-05T16:51:20Z 2008-10-05T16:51:20Z Mark Nottingham-2 <br>On 05/10/2008, at 7:11 AM, Adam Kropelin wrote: <br><div class='shrinkable-quote'><br>> Mark Nottingham wrote: <br>>> Hi, <br>>> <br>>> I've got a Back-UPS HS <br>>> <<a href="http://www.apcc.com/products/family/index.cfm?id=3" target="_top" rel="nofollow">http://www.apcc.com/products/family/index.cfm?id=3</a><br>>>> , which has ethernet, but no USB. Using nmap, it seems that the only <br>>> port that it listens on is 80 (HTTP), for the Web interface., but I <br>>> suspect that's not completely true, because it can be configured <br>>> remotely. <br>>> <br>>> Is it possible to monitor this device remotely over the network with <br>>> apcupsd? <br>> <br>> I actually own one of these UPSes...you and I may be the only people   <br>> who do <br>> :) </div><br>Heh. That's a shame; it's a nice little box. <br><br><div class='shrinkable-quote'><br>> I did some investigation several years ago and determined the HS has   <br>> only a <br>> web interface. The "remote configuration" is done by posting changes   <br>> to a <br>> web page on the unit, just like filling out a form on a real web   <br>> site. It <br>> would be possible for Apcupsd to read the current status of the UPS by <br>> requesting web pages and scraping the results off the page. I   <br>> considered <br>> writing a driver to do that, but decided to wait and see if there   <br>> was any <br>> interest first. You're the first to ever mention owning an HS... </div><br>I was thinking of writing a script like that; in my case I don't   <br>necessarily need it to be part of apcupsd, because i just need it to   <br>shut down my readynas box <<a href="http://www.readynas.com/" target="_top" rel="nofollow">http://www.readynas.com/</a>>. <br><br>Thanks, <br><br><br><div class='shrinkable-quote'><br>> <br>> <br>> --Adam <br>> <br>> <br>> ------------------------------------------------------------------------- <br>> This SF.Net email is sponsored by the Moblin Your Move Developer's   <br>> challenge <br>> Build the coolest Linux based applications with Moblin SDK & win   <br>> great prizes <br>> Grand prize is a trip for two to an Open Source event anywhere in   <br>> the world <br>> <a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/" target="_top" rel="nofollow">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a><br>> _______________________________________________ <br>> Apcupsd-users mailing list <br>> <a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19830295&i=0" target="_top" rel="nofollow">Apcupsd-users@...</a> <br>> <a href="https://lists.sourceforge.net/lists/listinfo/apcupsd-users" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a></div><br><br>-- <br>Mark Nottingham     <a href="http://www.mnot.net/" target="_top" rel="nofollow">http://www.mnot.net/</a><br><br><br>------------------------------------------------------------------------- <br>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge <br>Build the coolest Linux based applications with Moblin SDK & win great prizes <br>Grand prize is a trip for two to an Open Source event anywhere in the world <br><a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/" target="_top" rel="nofollow">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a><br>_______________________________________________ <br>Apcupsd-users mailing list <br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19830295&i=1" target="_top" rel="nofollow">Apcupsd-users@...</a> <br><a href="https://lists.sourceforge.net/lists/listinfo/apcupsd-users" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a><br><p>From forum: <a href="http://www.nabble.com/apcupsd-users-f3707.html" embed="fixTarget[3707]" target="_top" >apcupsd-users</a></p> tag:www.nabble.com,2006:post-19828447 Re: USB-cable: standard or proprietary? 2008-10-05T12:34:12Z 2008-10-05T12:34:12Z Kirill S. Bychkov Hi, Tom. Anyway you can find a lot of information about cable pinout in <br>apcupsd documentation. Also you can find it in the Internet. <br>I think the can't spoil USB interface so much - there are only 4 pins and <br>shield, so you can try a standard USB A-B cable with your UPS. <br><br>On Sun, October 5, 2008 21:21, Tom wrote: <div class='shrinkable-quote'><br>> Hello apcuspd-folks! <br>> <br>> <br>> <br>> I have learned in the past, that my APC UPSs with serial connection actually <br>> use special proprietary serial cables, rather than standard serial cables, <br>> isn't it?! <br>> <br>> <br>> <br>> Similar to that, one APC back-ups, that I own, that is supposed to have a <br>> USB connection, uses a proprietary cable, that has one  one side a USB jack <br>> and on the other side a jack that looks similar to RJ45 or something <br>> similar. <br>> <br>> <br>> <br>> Now I want to buy some used APCs via ebay. Many of them come without data <br>> cable unfortunately. <br>> <br>> <br>> <br>> Question: I saw that some devices, e.g. Smart-UPS 1000 come with a true <br>> USB-port at their rear, e.g. <br>> <a href="http://i14.ebayimg.com/04/i/001/0f/4a/5a7f_1.JPG" target="_top" rel="nofollow">http://i14.ebayimg.com/04/i/001/0f/4a/5a7f_1.JPG</a><br>> <br>> Can I buy such as device and just use any standard USB-Cable for this, or do <br>> these devices again need some proprietary APC-USB-cable? <br>> <br>> <br>> <br>> Best regards, <br>> <br>> tom <br>> <br>> <br>> <br>> ------------------------------------------------------------------------- <br>> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge <br>> Build the coolest Linux based applications with Moblin SDK & win great prizes <br>> Grand prize is a trip for two to an Open Source event anywhere in the world <br>> <a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________" target="_top" rel="nofollow">http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________</a><br>> Apcupsd-users mailing list <br>> <a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19828447&i=0" target="_top" rel="nofollow">Apcupsd-users@...</a> <br>> <a href="https://lists.sourceforge.net/lists/listinfo/apcupsd-users" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a><br>> </div><br><br>-- <br>()  ascii ribbon campaign - against html e-mail <br>/\  www.asciiribbon.org   - against proprietary attachments <br><br>------------------------------------------------------------------------- <br>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge <br>Build the coolest Linux based applications with Moblin SDK & win great prizes <br>Grand prize is a trip for two to an Open Source event anywhere in the world <br><a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/" target="_top" rel="nofollow">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a><br>_______________________________________________ <br>Apcupsd-users mailing list <br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19828447&i=1" target="_top" rel="nofollow">Apcupsd-users@...</a> <br><a href="https://lists.sourceforge.net/lists/listinfo/apcupsd-users" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a><br><p>From forum: <a href="http://www.nabble.com/apcupsd-users-f3707.html" embed="fixTarget[3707]" target="_top" >apcupsd-users</a></p> tag:www.nabble.com,2006:post-19827793 Re: USB-cable: standard or proprietary? 2008-10-05T11:08:57Z 2008-10-05T11:08:57Z Jernej Simončič-3 On Sunday, October 5, 2008, 19:21:08, Tom wrote: <br><br>> Can I buy such as device and just use any standard USB-Cable for this, or do <br>> these devices again need some proprietary APC-USB-cable? <br><br>In my (limited) experience, SmartUPSes use standard USB cables, while <br>BackUPSes use the RJ-45->USB cables. <br><br>-- <br>< Jernej Simončič ><><><><>< <a href="http://eternallybored.org/" target="_top" rel="nofollow">http://eternallybored.org/</a> > <br><br>Toothache tends to start on Saturday night. <br>       -- Laird's Law <br><br><br>------------------------------------------------------------------------- <br>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge <br>Build the coolest Linux based applications with Moblin SDK & win great prizes <br>Grand prize is a trip for two to an Open Source event anywhere in the world <br><a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/" target="_top" rel="nofollow">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a><br>_______________________________________________ <br>Apcupsd-users mailing list <br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19827793&i=0" target="_top" rel="nofollow">Apcupsd-users@...</a> <br><a href="https://lists.sourceforge.net/lists/listinfo/apcupsd-users" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a><br><p>From forum: <a href="http://www.nabble.com/apcupsd-users-f3707.html" embed="fixTarget[3707]" target="_top" >apcupsd-users</a></p> tag:www.nabble.com,2006:post-19826979 USB-cable: standard or proprietary? 2008-10-05T10:21:08Z 2008-10-05T10:21:08Z Tom-225 <html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 12 (filtered medium)">  </head> <body lang=DE link=blue vlink=purple> <div class=Section1> <p class=MsoNormal><span lang=EN-US>Hello apcuspd-folks!<o:p></o:p></span></p> <p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p> <p class=MsoNormal><span lang=EN-US>I have learned in the past, that my APC UPSs with serial connection actually use special proprietary serial cables, rather than standard serial cables, isn’t it?!<o:p></o:p></span></p> <p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p> <p class=MsoNormal><span lang=EN-US>Similar to that, one APC back-ups, that I own, that is supposed to have a USB connection, uses a proprietary cable, that has one  one side a USB jack and on the other side a jack that looks similar to RJ45 or something similar.<o:p></o:p></span></p> <p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p> <p class=MsoNormal><span lang=EN-US>Now I want to buy some used APCs via ebay. Many of them come without data cable unfortunately.<o:p></o:p></span></p> <p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p> <p class=MsoNormal><span lang=EN-US>Question: I saw that some devices, e.g. Smart-UPS 1000 come with a true USB-port at their rear, e.g. <a href="http://i14.ebayimg.com/04/i/001/0f/4a/5a7f_1.JPG" target="_top" rel="nofollow">http://i14.ebayimg.com/04/i/001/0f/4a/5a7f_1.JPG</a><o:p></o:p></span></p> <p class=MsoNormal><span lang=EN-US>Can I buy such as device and just use any standard USB-Cable for this, or do these devices again need some proprietary APC-USB-cable?<o:p></o:p></span></p> <p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p> <p class=MsoNormal><span lang=EN-US>Best regards,<o:p></o:p></span></p> <p class=MsoNormal><span lang=EN-US>tom</span><o:p></o:p></p> <p class=MsoNormal><o:p> </o:p></p> </div> </body> </html> <br />------------------------------------------------------------------------- <br>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge <br>Build the coolest Linux based applications with Moblin SDK & win great prizes <br>Grand prize is a trip for two to an Open Source event anywhere in the world <br><a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/" target="_top" rel="nofollow">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a><br />_______________________________________________ <br>Apcupsd-users mailing list <br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19826979&i=0" target="_top" rel="nofollow">Apcupsd-users@...</a> <br><a href="https://lists.sourceforge.net/lists/listinfo/apcupsd-users" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a><br><p>From forum: <a href="http://www.nabble.com/apcupsd-users-f3707.html" embed="fixTarget[3707]" target="_top" >apcupsd-users</a></p> tag:www.nabble.com,2006:post-19816901 Re: simple question 2008-10-04T13:14:47Z 2008-10-04T13:14:47Z Adam Kropelin Andrew Holt wrote: <br>> Hi, <br>> <br>> Is their a list that show the relation ship between the directives in <br>> apcupsd.conf and the event scripts(e.g. doshutdown) <br>> <br>> Something like: doshutdown runs if NETTIME MINUTES expire <br><br>There is no list in that format. There is documentation of the apcupsd.conf <br>directives in the sample apcupsd.conf file itself and in the apcupsd <br>manual. <br><br>--Adam <br><br><br>------------------------------------------------------------------------- <br>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge <br>Build the coolest Linux based applications with Moblin SDK & win great prizes <br>Grand prize is a trip for two to an Open Source event anywhere in the world <br><a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/" target="_top" rel="nofollow">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a><br>_______________________________________________ <br>Apcupsd-users mailing list <br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19816901&i=0" target="_top" rel="nofollow">Apcupsd-users@...</a> <br><a href="https://lists.sourceforge.net/lists/listinfo/apcupsd-users" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a><br><p>From forum: <a href="http://www.nabble.com/apcupsd-users-f3707.html" embed="fixTarget[3707]" target="_top" >apcupsd-users</a></p> tag:www.nabble.com,2006:post-19816836 Re: apcupsd + disabling servershudtown[VBSCL:A11CAA33173] 2008-10-04T13:14:07Z 2008-10-04T13:14:07Z Adam Kropelin Josef Karliak wrote: <br>> Hi, <br>> I've really stupid question - how to disable PC shutdown with apcupsd. <br>> I've about 15 apcupsd instances in one server for checking all UPS's, <br>> but this server may be shutdowned by UPS that has low battery, but <br>> this server is not powered by this one. Any kick off's for me ? :) <br>> THX. <br><br>Override the doshutdown event with a script of your own that tells <br>apccontrol not to perform default processing. (exit 99) See the apcupsd <br>manual for details on custom event handling. <br><br>--Adam <br><br><br>------------------------------------------------------------------------- <br>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge <br>Build the coolest Linux based applications with Moblin SDK & win great prizes <br>Grand prize is a trip for two to an Open Source event anywhere in the world <br><a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/" target="_top" rel="nofollow">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a><br>_______________________________________________ <br>Apcupsd-users mailing list <br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19816836&i=0" target="_top" rel="nofollow">Apcupsd-users@...</a> <br><a href="https://lists.sourceforge.net/lists/listinfo/apcupsd-users" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a><br><p>From forum: <a href="http://www.nabble.com/apcupsd-users-f3707.html" embed="fixTarget[3707]" target="_top" >apcupsd-users</a></p> tag:www.nabble.com,2006:post-19819532 Re: PCnet authentication failure- adifferent problem 2008-10-04T13:12:28Z 2008-10-04T13:12:28Z Adam Kropelin Philip Tait wrote: <div class='shrinkable-quote'><br>> Finally got an opportunity to update the firmware: <br>> <br>> Name: sumx Version: v3.5.7 Date: 08/13/2008 Time: 20:18:13 <br>> Name: aos Version: v3.6.1 Date: 08/13/2008 Time: 18:49:49 <br>> <br>> apcaccess reports: <br>> <br>> APC      : 001,019,0478 <br>> DATE     : Mon Sep 29 14:14:27 HST 2008 <br>> HOSTNAME : irs1 <br>> RELEASE  : 3.14.4 <br>> VERSION  : 3.14.4 (18 May 2008) redhat <br>> UPSNAME  : irs2-ups1 <br>> CABLE    : Ethernet Link <br>> MODEL    : PCNET UPS Driver <br>> UPSMODE  : Stand Alone <br>> STARTTIME: Mon Sep 29 14:11:03 HST 2008 <br>> STATUS   : COMMLOST <br>> MBATTCHG : 5 Percent <br>> MINTIMEL : 3 Minutes <br>> MAXTIME  : 0 Seconds <br>> NUMXFERS : 0 <br>> TONBATT  : 0 seconds <br>> CUMONBATT: 0 seconds <br>> XOFFBATT : N/A <br>> STATFLAG : 0x07000100 Status Flag <br>> END APC  : Mon Sep 29 14:14:27 HST 2008 <br>> <br>> Debug output from apcupsd ("NO CI_VLINE" is output when apcaccess is <br>> run): </div><br>Apcupsd is not receiving any updates from the UPS (thus the COMMLIST <br>state). Go into the web interface for the UPS and ensure it is set to send <br>updates to your server. <br><br>--Adam <br><br><br>------------------------------------------------------------------------- <br>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge <br>Build the coolest Linux based applications with Moblin SDK & win great prizes <br>Grand prize is a trip for two to an Open Source event anywhere in the world <br><a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/" target="_top" rel="nofollow">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a><br>_______________________________________________ <br>Apcupsd-users mailing list <br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19819532&i=0" target="_top" rel="nofollow">Apcupsd-users@...</a> <br><a href="https://lists.sourceforge.net/lists/listinfo/apcupsd-users" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a><br><p>From forum: <a href="http://www.nabble.com/apcupsd-users-f3707.html" embed="fixTarget[3707]" target="_top" >apcupsd-users</a></p> tag:www.nabble.com,2006:post-19816834 Re: Back-UPS HS? 2008-10-04T13:11:30Z 2008-10-04T13:11:30Z Adam Kropelin Mark Nottingham wrote: <div class='shrinkable-quote'><br>> Hi, <br>> <br>> I've got a Back-UPS HS <br>> <<a href="http://www.apcc.com/products/family/index.cfm?id=3" target="_top" rel="nofollow">http://www.apcc.com/products/family/index.cfm?id=3</a><br>>> , which has ethernet, but no USB. Using nmap, it seems that the only <br>> port that it listens on is 80 (HTTP), for the Web interface., but I <br>> suspect that's not completely true, because it can be configured <br>> remotely. <br>> <br>> Is it possible to monitor this device remotely over the network with <br>> apcupsd? </div><br>I actually own one of these UPSes...you and I may be the only people who do <br>:) <br><br>I did some investigation several years ago and determined the HS has only a <br>web interface. The "remote configuration" is done by posting changes to a <br>web page on the unit, just like filling out a form on a real web site. It <br>would be possible for Apcupsd to read the current status of the UPS by <br>requesting web pages and scraping the results off the page. I considered <br>writing a driver to do that, but decided to wait and see if there was any <br>interest first. You're the first to ever mention owning an HS... <br><br>--Adam <br><br><br>------------------------------------------------------------------------- <br>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge <br>Build the coolest Linux based applications with Moblin SDK & win great prizes <br>Grand prize is a trip for two to an Open Source event anywhere in the world <br><a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/" target="_top" rel="nofollow">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a><br>_______________________________________________ <br>Apcupsd-users mailing list <br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19816834&i=0" target="_top" rel="nofollow">Apcupsd-users@...</a> <br><a href="https://lists.sourceforge.net/lists/listinfo/apcupsd-users" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a><br><p>From forum: <a href="http://www.nabble.com/apcupsd-users-f3707.html" embed="fixTarget[3707]" target="_top" >apcupsd-users</a></p> tag:www.nabble.com,2006:post-19816753 Re: Irritating bug? APC Smart UPS on USB (linux):Return Threshold 2008-10-04T13:07:49Z 2008-10-04T13:07:49Z Adam Kropelin Bob Freemer wrote: <br>> I have determined this is a bug in APCUPSD by using APC's Powerchute <br>> software (on a Windows machine) to write the eeprom to 75% and 90%. <br>> After then switching the USB to the linux machine, verifying the <br>> "RETPCT" value is 090.0 using apcaccess, and pulling the UPS plug, <br>> apcupsd does a very graceful shutdown as expected.  However, when <br>> the power is thereafter restored to the UPS, it restores load power <br>> even if batteries are depleted. After the machine boots up in this <br>> circumstance, I find the "RETPCT" value of 000.0. <br><br>We do hardcode RETPCT to 0 on USB models, largely to stem the flow of "My <br>UPS does not turn on after power returns" emails from folks who simply did <br>not wait long enough. I do have plans to make the value configurable at <br>runtime, but for now you can simply edit the code in src/drivers/usb/usb.c <br>to set whatever value you want (or comment-out the code that sets it to <br>anything at all). <br><br>--Adam <br><br><br>------------------------------------------------------------------------- <br>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge <br>Build the coolest Linux based applications with Moblin SDK & win great prizes <br>Grand prize is a trip for two to an Open Source event anywhere in the world <br><a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/" target="_top" rel="nofollow">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a><br>_______________________________________________ <br>Apcupsd-users mailing list <br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19816753&i=0" target="_top" rel="nofollow">Apcupsd-users@...</a> <br><a href="https://lists.sourceforge.net/lists/listinfo/apcupsd-users" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a><br><p>From forum: <a href="http://www.nabble.com/apcupsd-users-f3707.html" embed="fixTarget[3707]" target="_top" >apcupsd-users</a></p> tag:www.nabble.com,2006:post-19807639 Re: APCUPSD Manual ( was BAT with older director) 2008-10-03T17:01:07Z 2008-10-03T17:01:07Z Joseph L. Casale >Any advice to get a working manual for the version I have? <br><br><a href="http://www.apcupsd.org/" target="_top" rel="nofollow">http://www.apcupsd.org/</a><br><br>Look on the left :) <br><br>------------------------------------------------------------------------- <br>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge <br>Build the coolest Linux based applications with Moblin SDK & win great prizes <br>Grand prize is a trip for two to an Open Source event anywhere in the world <br><a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/" target="_top" rel="nofollow">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a><br>_______________________________________________ <br>Apcupsd-users mailing list <br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19807639&i=0" target="_top" rel="nofollow">Apcupsd-users@...</a> <br><a href="https://lists.sourceforge.net/lists/listinfo/apcupsd-users" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a><br><p>From forum: <a href="http://www.nabble.com/apcupsd-users-f3707.html" embed="fixTarget[3707]" target="_top" >apcupsd-users</a></p> tag:www.nabble.com,2006:post-19807185 APCUPSD Manual ( was BAT with older director) 2008-10-03T16:07:41Z 2008-10-03T16:07:41Z Steve Garcia Steve Garcia wrote: <br>> (I'm re-sending this, since I'm not sure it went out the first time...) <br>> <br>> I just built BAT on my workstation.  The version that got built on <br>> Gentoo is 2.4.2, which is the most current version as I understand it. <br><br>Oops!  My apologies.  Wrong list! <br><br>I actually intended to ask a different question on this list. <br><br>I'm looking for a copy of the manual for apcupsd 3.12.4.  I've installed <br>it on Debian Etch, and I found the tex files for the manual, but haven't <br>been able to do anything with them.  I've gunzipped all the files that <br>need to be (I think) but still get errors. <br><br>Make seems to bomb no matter what I do.  Right now it's looking for <br>apcupsd.idx. <br><br>It's probably something to do with the way that Debian packaged up the <br>files.  Any advice to get a working manual for the version I have? <br><br><br>-- <br>Steve Garcia <br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19807185&i=0" target="_top" rel="nofollow">sgarcia@...</a> <br>Ignorance killed the cat; Curiosity was framed. <br><br>------------------------------------------------------------------------- <br>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge <br>Build the coolest Linux based applications with Moblin SDK & win great prizes <br>Grand prize is a trip for two to an Open Source event anywhere in the world <br><a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/" target="_top" rel="nofollow">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a><br>_______________________________________________ <br>Apcupsd-users mailing list <br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19807185&i=1" target="_top" rel="nofollow">Apcupsd-users@...</a> <br><a href="https://lists.sourceforge.net/lists/listinfo/apcupsd-users" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a><br><p>From forum: <a href="http://www.nabble.com/apcupsd-users-f3707.html" embed="fixTarget[3707]" target="_top" >apcupsd-users</a></p> tag:www.nabble.com,2006:post-19807289 Re: BAT with older director 2008-10-03T16:02:51Z 2008-10-03T16:02:51Z Reuti Hi, <br><br>BAT?!? Maybe you ended up on the wrong list. <br><br>-- Reuti <br><br><br>Am 04.10.2008 um 00:37 schrieb Steve Garcia: <br><div class='shrinkable-quote'><br>> (I'm re-sending this, since I'm not sure it went out the first   <br>> time...) <br>> <br>> I just built BAT on my workstation.  The version that got built on <br>> Gentoo is 2.4.2, which is the most current version as I understand it. <br>> <br>> The actual running server is on Debian Etch, and is the packaged   <br>> version <br>> for Etch, namely 1.38. <br>> <br>> When I fire up BAT, it connects to the director with only one minor <br>> problem:  after the connect line <br>> <br>> 1000 OK: sleipnir-dir Version: 1.38.11  (28 June 2006) <br>> <br>> I get an error line <br>> <br>> .api 1: is an illegal command <br>> <br>>> From this point, console commands work fine.  Most of the other <br>> controls, however, cause a dialog box to come up with a message   <br>> telling <br>> me that "Director sleipnir-dir is currently busy" <br>> <br>> An earlier message on the mailing list indicated that this might be a <br>> cosmetic bug with BAT 2.4.2, and that functionality was not impacted. <br>> However, it doesn't seem to be true here -- Other than the console, I <br>> can get no information from BAT. <br>> <br>> Is this an incompatibility between this version of BAT and 1.38 of the <br>> director?  If so, I'll just stick with the console for the moment. <br>> <br>> -- <br>> Steve Garcia <br>> <a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19807289&i=0" target="_top" rel="nofollow">sgarcia@...</a> <br>> Ignorance killed the cat; Curiosity was framed. <br>> <br>> ---------------------------------------------------------------------- <br>> --- <br>> This SF.Net email is sponsored by the Moblin Your Move Developer's   <br>> challenge <br>> Build the coolest Linux based applications with Moblin SDK & win   <br>> great prizes <br>> Grand prize is a trip for two to an Open Source event anywhere in   <br>> the world <br>> <a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/" target="_top" rel="nofollow">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a><br>> _______________________________________________ <br>> Apcupsd-users mailing list <br>> <a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19807289&i=1" target="_top" rel="nofollow">Apcupsd-users@...</a> <br>> <a href="https://lists.sourceforge.net/lists/listinfo/apcupsd-users" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a></div><br><br>------------------------------------------------------------------------- <br>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge <br>Build the coolest Linux based applications with Moblin SDK & win great prizes <br>Grand prize is a trip for two to an Open Source event anywhere in the world <br><a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/" target="_top" rel="nofollow">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a><br>_______________________________________________ <br>Apcupsd-users mailing list <br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19807289&i=2" target="_top" rel="nofollow">Apcupsd-users@...</a> <br><a href="https://lists.sourceforge.net/lists/listinfo/apcupsd-users" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a><br><p>From forum: <a href="http://www.nabble.com/apcupsd-users-f3707.html" embed="fixTarget[3707]" target="_top" >apcupsd-users</a></p> tag:www.nabble.com,2006:post-19806932 BAT with older director 2008-10-03T15:37:30Z 2008-10-03T15:37:30Z Steve Garcia (I'm re-sending this, since I'm not sure it went out the first time...) <br><br>I just built BAT on my workstation.  The version that got built on <br>Gentoo is 2.4.2, which is the most current version as I understand it. <br><br>The actual running server is on Debian Etch, and is the packaged version <br>for Etch, namely 1.38. <br><br>When I fire up BAT, it connects to the director with only one minor <br>problem:  after the connect line <br><br>1000 OK: sleipnir-dir Version: 1.38.11  (28 June 2006) <br><br>I get an error line <br><br>.api 1: is an illegal command <br><br>>From this point, console commands work fine.  Most of the other <br>controls, however, cause a dialog box to come up with a message telling <br>me that "Director sleipnir-dir is currently busy" <br><br>An earlier message on the mailing list indicated that this might be a <br>cosmetic bug with BAT 2.4.2, and that functionality was not impacted. <br>However, it doesn't seem to be true here -- Other than the console, I <br>can get no information from BAT. <br><br>Is this an incompatibility between this version of BAT and 1.38 of the <br>director?  If so, I'll just stick with the console for the moment. <br><br>-- <br>Steve Garcia <br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19806932&i=0" target="_top" rel="nofollow">sgarcia@...</a> <br>Ignorance killed the cat; Curiosity was framed. <br><br>------------------------------------------------------------------------- <br>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge <br>Build the coolest Linux based applications with Moblin SDK & win great prizes <br>Grand prize is a trip for two to an Open Source event anywhere in the world <br><a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/" target="_top" rel="nofollow">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a><br>_______________________________________________ <br>Apcupsd-users mailing list <br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19806932&i=1" target="_top" rel="nofollow">Apcupsd-users@...</a> <br><a href="https://lists.sourceforge.net/lists/listinfo/apcupsd-users" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a><br><p>From forum: <a href="http://www.nabble.com/apcupsd-users-f3707.html" embed="fixTarget[3707]" target="_top" >apcupsd-users</a></p> tag:www.nabble.com,2006:post-19818318 Compatibility with very old smart-ups'es (SU600I, SU2000I) 2008-10-03T00:41:17Z 2008-10-03T00:41:17Z Michal Soltys-2 I have a few very old upses (models as mentioned in subject) - some of <br>them work fine with apcupsd/apctest, whereas some others don't react to <br>'a' command, causing both apctest and apcupsd to wait indefinitely for <br>its results. <br><br>Is there any way / workaround to get them working under apcupsd control ? <br><br><br><br>------------------------------------------------------------------------- <br>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge <br>Build the coolest Linux based applications with Moblin SDK & win great prizes <br>Grand prize is a trip for two to an Open Source event anywhere in the world <br><a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/" target="_top" rel="nofollow">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a><br>_______________________________________________ <br>Apcupsd-users mailing list <br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19818318&i=0" target="_top" rel="nofollow">Apcupsd-users@...</a> <br><a href="https://lists.sourceforge.net/lists/listinfo/apcupsd-users" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a><br><p>From forum: <a href="http://www.nabble.com/apcupsd-users-f3707.html" embed="fixTarget[3707]" target="_top" >apcupsd-users</a></p> tag:www.nabble.com,2006:post-19818018 USB Interface on NetBSD 2008-10-02T11:55:20Z 2008-10-02T11:55:20Z Alfonso Elefante <div dir="ltr"><div>I recently bought an APC UPS (Back-UPS ES 700, with USB Interface) to protect my Soekris NET5501 system running Netbsd 4.0. Before installing apcupsd on Netbsd, I recompiled the kernel to force ugen device detection (as explained in apcupsd manual), but:</div> <div> </div> <div>- if I plug the USB cable into the NET5501 system after it has booted, the UPS is correctly detected by the system (as ugen0) and apcupsd runs and is connected to the UPS;<br>- if I boot the system (both hot/cold reboot) with the UPS USB cable already plugged-in, the system doesn't detect the UPS and apcupsd start fails. If I unplug and replug the USB cable into the system, it correctly sees the UPS and, after restarting apcupsd, it works again.</div> <div> </div> <div>Do someone have a solution or any suggestion?</div> <div> </div> <div>If you need further information, please ask me, thank you.</div></div> <br />------------------------------------------------------------------------- <br>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge <br>Build the coolest Linux based applications with Moblin SDK & win great prizes <br>Grand prize is a trip for two to an Open Source event anywhere in the world <br><a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/" target="_top" rel="nofollow">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a><br />_______________________________________________ <br>Apcupsd-users mailing list <br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19818018&i=0" target="_top" rel="nofollow">Apcupsd-users@...</a> <br><a href="https://lists.sourceforge.net/lists/listinfo/apcupsd-users" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/apcupsd-users</a><br><p>From forum: <a href="http://www.nabble.com/apcupsd-users-f3707.html" embed="fixTarget[3707]" target="_top" >apcupsd-users</a></p> tag:www.nabble.com,2006:post-19831591 Make Problem with 3.14.4(solaris8) 2008-10-01T02:10:10Z 2008-10-01T02:10:10Z 原田雄太 I have a problem with make apcupsd3.14.4. <br>When I try to make apcupsd3.14.4, I got a messages below. <br>(Or see the attached text) <br>-----messages----- <br>In file included from /home/work/apcupsd-3.14.4/include/apc.h:92, <br>                 from apcconfig.c:28: <br>/usr/include/sys/ioctl.h:68: warning: `ECHO' redefined <br>/usr/include/sys/termios.h:295: warning: this is the location of the <br>previous definition <br>/usr/include/sys/ioctl.h:75: warning: `NL0' redefined <br>/usr/include/sys/termios.h:219: warning: this is the location of the <br>previous definition <br>------------------ <br>-----Environment----- <br>apcupsd3.10.8 <br>apcupsd3.14.4 <br><br>OS: <br>solaris8(SUNWCreq) <br><br>Apps: <br>gzip1.3.5 <br>gcc-2.95.3 <br>libgcc-3.0 <br>make-3.80 <br>-------------------- <br>I can make apcupsd3.10.18 by same procedure. <br><br>Any wrong with my procedure? <br>Please help me! <br><br>Thank you. <br><br>Harada <br><br />$ ./configure \ <br>> --prefix=/opt/apcupsd \ <br>> --sbindir=/etc/opt/apcupsd/sbin \ <br>> --sysconfdir=/etc/opt/apcupsd \ <br>> --enable-master-slave \ <br>> --enable-net \ <br>> --with-net-port=6666 <br>checking for true... /usr/bin/true <br>checking for false... /usr/bin/false <br>checking build system type... sparc-sun-solaris2.8 <br>checking host system type... sparc-sun-solaris2.8 <br>checking for gcc... gcc <br>checking for C compiler default output file name... a.out <br>checking whether the C compiler works... yes <br>checking whether we are cross compiling... no <br>checking for suffix of executables... <br>checking for suffix of object files... o <br>checking whether we are using the GNU C compiler... yes <br>checking whether gcc accepts -g... yes <br>checking for gcc option to accept ANSI C... none needed <br>checking how to run the C preprocessor... gcc -E <br>checking for g++... g++ <br>checking whether we are using the GNU C++ compiler... yes <br>checking whether g++ accepts -g... yes <br>checking whether gcc and cc understand -c and -o together... yes <br>checking for egrep... egrep <br>checking whether gcc needs -traditional... no <br>checking for a BSD-compatible install... /home/work/apcupsd-3.14.4/autoconf/install-sh -c <br>checking for gawk... no <br>checking for mawk... no <br>checking for nawk... nawk <br>checking for library containing strerror... none required <br>checking for shutdown... /usr/sbin/shutdown <br>checking for mail... /usr/bin/mail <br>checking for wall... /usr/sbin/wall <br>checking for sh... /usr/bin/sh <br>checking for GNU make... make <br>checking for ranlib... /usr/ccs/bin/ranlib <br>checking for rm... /usr/bin/rm <br>checking for cp... /usr/bin/cp <br>checking for echo... /usr/bin/echo <br>checking for ln... /usr/bin/ln <br>checking for sed... /usr/bin/sed <br>checking for ar... /usr/ccs/bin/ar <br>checking for mv... /usr/bin/mv <br>checking for abort... yes <br>checking for fork... yes <br>checking for calloc... yes <br>checking for getpid... yes <br>checking for ioctl... yes <br>checking for kill... yes <br>checking for rewind... yes <br>checking for select... yes <br>checking for setsid... yes <br>checking for signal... yes <br>checking for strerror... yes <br>checking for strncmp... yes <br>checking for strncpy... yes <br>checking for tcgetattr... yes <br>checking for vfprintf... yes <br>checking for setpgrp... yes <br>checking for snprintf... yes <br>checking for vsnprintf... yes <br>checking for library containing nanosleep... -lrt <br>checking for syslog... yes <br>checking for strftime... yes <br>checking whether setpgrp takes no argument... yes <br>checking for library containing socket... -lxnet <br>checking for library containing gethostname... none required <br>checking for library containing gethostbyname... none required <br>checking for library containing gethostbyname_r... -lnsl <br>checking for socklen_t... yes <br>checking for library containing inet_addr... none required <br>checking for strchr... yes <br>using libc's strchr <br>checking for strstr... yes <br>checking for strcasecmp... yes <br>checking for memmove... yes <br>checking for getopt_long... no <br>checking for inet_pton... yes <br>checking for localtime_r... yes <br>checking for ANSI C header files... yes <br>checking for sys/types.h... yes <br>checking for sys/stat.h... yes <br>checking for stdlib.h... yes <br>checking for string.h... yes <br>checking for memory.h... yes <br>checking for strings.h... yes <br>checking for inttypes.h... yes <br>checking for stdint.h... no <br>checking for unistd.h... yes <br>checking arpa/inet.h usability... yes <br>checking arpa/inet.h presence... yes <br>checking for arpa/inet.h... yes <br>checking ctype.h usability... yes <br>checking ctype.h presence... yes <br>checking for ctype.h... yes <br>checking errno.h usability... yes <br>checking errno.h presence... yes <br>checking for errno.h... yes <br>checking fcntl.h usability... yes <br>checking fcntl.h presence... yes <br>checking for fcntl.h... yes <br>checking limits.h usability... yes <br>checking limits.h presence... yes <br>checking for limits.h... yes <br>checking netdb.h usability... yes <br>checking netdb.h presence... yes <br>checking for netdb.h... yes <br>checking netinet/in.h usability... yes <br>checking netinet/in.h presence... yes <br>checking for netinet/in.h... yes <br>checking pwd.h usability... yes <br>checking pwd.h presence... yes <br>checking for pwd.h... yes <br>checking signal.h usability... yes <br>checking signal.h presence... yes <br>checking for signal.h... yes <br>checking stdarg.h usability... yes <br>checking stdarg.h presence... yes <br>checking for stdarg.h... yes <br>checking stdio.h usability... yes <br>checking stdio.h presence... yes <br>checking for stdio.h... yes <br>checking for stdlib.h... (cached) yes <br>checking for string.h... (cached) yes <br>checking for strings.h... (cached) yes <br>checking sys/ioctl.h usability... yes <br>checking sys/ioctl.h presence... yes <br>checking for sys/ioctl.h... yes <br>checking sys/socket.h usability... yes <br>checking sys/socket.h presence... yes <br>checking for sys/socket.h... yes <br>checking for sys/types.h... (cached) yes <br>checking syslog.h usability... yes <br>checking syslog.h presence... yes <br>checking for syslog.h... yes <br>checking termios.h usability... yes <br>checking termios.h presence... yes <br>checking for termios.h... yes <br>checking for unistd.h... (cached) yes <br>checking arpa/nameser.h usability... yes <br>checking arpa/nameser.h presence... yes <br>checking for arpa/nameser.h... yes <br>checking whether stat file-mode macros are broken... no <br>checking whether time.h and sys/time.h may both be included... yes <br>checking for sys/wait.h that is POSIX.1 compatible... yes <br>checking whether struct tm is in sys/time.h or time.h... time.h <br>checking for struct tm.tm_zone... no <br>checking for tzname... yes <br>checking for uid_t in sys/types.h... yes <br>checking type of array argument to getgroups... gid_t <br>checking for mode_t... yes <br>checking for off_t... yes <br>checking for pid_t... yes <br>checking return type of signal handlers... void <br>checking for size_t... yes <br>checking for uid_t in sys/types.h... (cached) yes <br>checking for socklen_t... yes <br>checking for int32_t... yes <br>checking for X... libraries /usr/openwin/lib, headers /usr/openwin/include <br>checking whether -R must be followed by a space... no <br>checking for gethostbyname... yes <br>checking for connect... yes <br>checking for remove... yes <br>checking for shmat... yes <br>checking for IceConnectionNumber in -lICE... yes <br>checking whether #! works in shell scripts... yes <br>Will not install HAL policy file <br>checking for pkg-config... no <br>checking if libsupc++ is required... no <br>checking if GCC supports -fno-exceptions... yes <br>checking if GCC supports -fno-rtti... yes <br>checking for wait... yes <br>checking for waitpid... yes <br>checking for wait3... yes <br>checking for union wait... no <br>Disabling cgi support... <br>gcc private include directory found. <br>configure: creating ./config.status <br>config.status: creating autoconf/variables.mak <br>config.status: creating platforms/apccontrol <br>config.status: creating platforms/etc/changeme <br>config.status: creating platforms/etc/commfailure <br>config.status: creating platforms/etc/commok <br>config.status: creating platforms/etc/offbattery <br>config.status: creating platforms/etc/onbattery <br>config.status: creating platforms/etc/apcupsd.conf <br>config.status: creating examples/safe.apccontrol <br>config.status: creating src/win32/Makefile <br>config.status: creating platforms/sun/apcupsd <br>config.status: creating platforms/sun/rc0.solaris <br>config.status: creating platforms/sun/apccontrol <br>config.status: creating include/config.h <br><br><br>Configuration on Wed Oct  1 15:21:53 JST 2008: <br><br>  Host:                       sparc-sun-solaris2.8 -- sun Solaris <br>  Apcupsd version:            3.14.4 (18 May 2008) <br>  Source code location:       . <br>  Install binaries:           /etc/opt/apcupsd/sbin <br>  Install config files:       /etc/opt/apcupsd <br>  Install man files:          /usr/share/man <br>  Nologin file in:            /etc <br>  PID directory:              /var/run <br>  LOG dir (events, status)    /etc/opt/apcupsd <br>  LOCK dir (for serial port)  /var/spool/locks <br>  Power Fail dir              /etc <br>  Compiler:                   g++ 2.95.3 <br>  Compiler flags:             -g -O2 -Wall <br>  Linker:                     gcc <br>  Linker flags:               -g -O <br>  Host and version:           sun Solaris <br>  Shutdown Program:           /usr/sbin/shutdown <br>  Port/Device:                /dev/ttya <br>  Network Info Port (CGI):    3551 <br>  UPSTYPE                     apcsmart <br>  UPSCABLE                    smart <br><br>  drivers (no-* are disabled): apcsmart dumb net no-usb no-snmp pcnet no-test <br><br>  enable-nis:                 yes <br>  with-nisip:                 0.0.0.0 <br>  enable-cgi:                 no <br>  with-cgi-bin:               /etc/apcupsd <br>  with-libwrap: <br>  enable-powerflute:          no <br>  enable-pthreads:            yes <br>  enable-dist-install:        yes <br>  enable-gapcmon:             no <br><br>Configuration complete: Run 'make' to build apcuspd. <br><br>$ make <br>        src <br>        src/lib <br>  CXX   src/lib/apcconfig.c <br>In file included from /home/work/apcupsd-3.14.4/include/apc.h:92, <br>                 from apcconfig.c:28: <br>/usr/include/sys/ioctl.h:68: warning: `ECHO' redefined <br>/usr/include/sys/termios.h:295: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:75: warning: `NL0' redefined <br>/usr/include/sys/termios.h:219: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:76: warning: `NL1' redefined <br>/usr/include/sys/termios.h:220: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:80: warning: `TAB0' redefined <br>/usr/include/sys/termios.h:227: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:81: warning: `TAB1' redefined <br>/usr/include/sys/termios.h:228: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:82: warning: `TAB2' redefined <br>/usr/include/sys/termios.h:229: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:83: warning: `XTABS' redefined <br>/usr/include/sys/termios.h:234: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:85: warning: `CR0' redefined <br>/usr/include/sys/termios.h:222: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:86: warning: `CR1' redefined <br>/usr/include/sys/termios.h:223: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:87: warning: `CR2' redefined <br>/usr/include/sys/termios.h:224: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:88: warning: `CR3' redefined <br>/usr/include/sys/termios.h:225: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:90: warning: `FF0' redefined <br>/usr/include/sys/termios.h:245: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:91: warning: `FF1' redefined <br>/usr/include/sys/termios.h:246: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:93: warning: `BS0' redefined <br>/usr/include/sys/termios.h:239: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:94: warning: `BS1' redefined <br>/usr/include/sys/termios.h:240: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:103: warning: `TOSTOP' redefined <br>/usr/include/sys/termios.h:300: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:104: warning: `FLUSHO' redefined <br>/usr/include/sys/termios.h:307: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:110: warning: `PENDIN' redefined <br>/usr/include/sys/termios.h:308: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:112: warning: `NOFLSH' redefined <br>/usr/include/sys/termios.h:299: warning: this is the location of the previous definition <br>In file included from /home/work/apcupsd-3.14.4/include/apc.h:92, <br>                 from apcconfig.c:28: <br>/usr/include/sys/ioctl.h:68: warning: `ECHO' redefined <br>/usr/include/sys/termios.h:295: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:75: warning: `NL0' redefined <br>/usr/include/sys/termios.h:219: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:76: warning: `NL1' redefined <br>/usr/include/sys/termios.h:220: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:80: warning: `TAB0' redefined <br>/usr/include/sys/termios.h:227: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:81: warning: `TAB1' redefined <br>/usr/include/sys/termios.h:228: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:82: warning: `TAB2' redefined <br>/usr/include/sys/termios.h:229: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:83: warning: `XTABS' redefined <br>/usr/include/sys/termios.h:234: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:85: warning: `CR0' redefined <br>/usr/include/sys/termios.h:222: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:86: warning: `CR1' redefined <br>/usr/include/sys/termios.h:223: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:87: warning: `CR2' redefined <br>/usr/include/sys/termios.h:224: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:88: warning: `CR3' redefined <br>/usr/include/sys/termios.h:225: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:90: warning: `FF0' redefined <br>/usr/include/sys/termios.h:245: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:91: warning: `FF1' redefined <br>/usr/include/sys/termios.h:246: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:93: warning: `BS0' redefined <br>/usr/include/sys/termios.h:239: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:94: warning: `BS1' redefined <br>/usr/include/sys/termios.h:240: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:103: warning: `TOSTOP' redefined <br>/usr/include/sys/termios.h:300: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:104: warning: `FLUSHO' redefined <br>/usr/include/sys/termios.h:307: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:110: warning: `PENDIN' redefined <br>/usr/include/sys/termios.h:308: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:112: warning: `NOFLSH' redefined <br>/usr/include/sys/termios.h:299: warning: this is the location of the previous definition <br>  CXX   src/lib/apcerror.c <br>In file included from /home/work/apcupsd-3.14.4/include/apc.h:92, <br>                 from apcerror.c:26: <br>/usr/include/sys/ioctl.h:68: warning: `ECHO' redefined <br>/usr/include/sys/termios.h:295: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:75: warning: `NL0' redefined <br>/usr/include/sys/termios.h:219: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:76: warning: `NL1' redefined <br>/usr/include/sys/termios.h:220: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:80: warning: `TAB0' redefined <br>/usr/include/sys/termios.h:227: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:81: warning: `TAB1' redefined <br>/usr/include/sys/termios.h:228: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:82: warning: `TAB2' redefined <br>/usr/include/sys/termios.h:229: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:83: warning: `XTABS' redefined <br>/usr/include/sys/termios.h:234: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:85: warning: `CR0' redefined <br>/usr/include/sys/termios.h:222: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:86: warning: `CR1' redefined <br>/usr/include/sys/termios.h:223: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:87: warning: `CR2' redefined <br>/usr/include/sys/termios.h:224: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:88: warning: `CR3' redefined <br>/usr/include/sys/termios.h:225: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:90: warning: `FF0' redefined <br>/usr/include/sys/termios.h:245: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:91: warning: `FF1' redefined <br>/usr/include/sys/termios.h:246: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:93: warning: `BS0' redefined <br>/usr/include/sys/termios.h:239: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:94: warning: `BS1' redefined <br>/usr/include/sys/termios.h:240: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:103: warning: `TOSTOP' redefined <br>/usr/include/sys/termios.h:300: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:104: warning: `FLUSHO' redefined <br>/usr/include/sys/termios.h:307: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:110: warning: `PENDIN' redefined <br>/usr/include/sys/termios.h:308: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:112: warning: `NOFLSH' redefined <br>/usr/include/sys/termios.h:299: warning: this is the location of the previous definition <br>In file included from /home/work/apcupsd-3.14.4/include/apc.h:92, <br>                 from apcerror.c:26: <br>/usr/include/sys/ioctl.h:68: warning: `ECHO' redefined <br>/usr/include/sys/termios.h:295: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:75: warning: `NL0' redefined <br>/usr/include/sys/termios.h:219: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:76: warning: `NL1' redefined <br>/usr/include/sys/termios.h:220: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:80: warning: `TAB0' redefined <br>/usr/include/sys/termios.h:227: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:81: warning: `TAB1' redefined <br>/usr/include/sys/termios.h:228: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:82: warning: `TAB2' redefined <br>/usr/include/sys/termios.h:229: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:83: warning: `XTABS' redefined <br>/usr/include/sys/termios.h:234: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:85: warning: `CR0' redefined <br>/usr/include/sys/termios.h:222: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:86: warning: `CR1' redefined <br>/usr/include/sys/termios.h:223: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:87: warning: `CR2' redefined <br>/usr/include/sys/termios.h:224: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:88: warning: `CR3' redefined <br>/usr/include/sys/termios.h:225: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:90: warning: `FF0' redefined <br>/usr/include/sys/termios.h:245: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:91: warning: `FF1' redefined <br>/usr/include/sys/termios.h:246: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:93: warning: `BS0' redefined <br>/usr/include/sys/termios.h:239: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:94: warning: `BS1' redefined <br>/usr/include/sys/termios.h:240: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:103: warning: `TOSTOP' redefined <br>/usr/include/sys/termios.h:300: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:104: warning: `FLUSHO' redefined <br>/usr/include/sys/termios.h:307: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:110: warning: `PENDIN' redefined <br>/usr/include/sys/termios.h:308: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:112: warning: `NOFLSH' redefined <br>/usr/include/sys/termios.h:299: warning: this is the location of the previous definition <br>  CXX   src/lib/apcevents.c <br>In file included from /home/work/apcupsd-3.14.4/include/apc.h:92, <br>                 from apcevents.c:25: <br>/usr/include/sys/ioctl.h:68: warning: `ECHO' redefined <br>/usr/include/sys/termios.h:295: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:75: warning: `NL0' redefined <br>/usr/include/sys/termios.h:219: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:76: warning: `NL1' redefined <br>/usr/include/sys/termios.h:220: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:80: warning: `TAB0' redefined <br>/usr/include/sys/termios.h:227: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:81: warning: `TAB1' redefined <br>/usr/include/sys/termios.h:228: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:82: warning: `TAB2' redefined <br>/usr/include/sys/termios.h:229: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:83: warning: `XTABS' redefined <br>/usr/include/sys/termios.h:234: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:85: warning: `CR0' redefined <br>/usr/include/sys/termios.h:222: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:86: warning: `CR1' redefined <br>/usr/include/sys/termios.h:223: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:87: warning: `CR2' redefined <br>/usr/include/sys/termios.h:224: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:88: warning: `CR3' redefined <br>/usr/include/sys/termios.h:225: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:90: warning: `FF0' redefined <br>/usr/include/sys/termios.h:245: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:91: warning: `FF1' redefined <br>/usr/include/sys/termios.h:246: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:93: warning: `BS0' redefined <br>/usr/include/sys/termios.h:239: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:94: warning: `BS1' redefined <br>/usr/include/sys/termios.h:240: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:103: warning: `TOSTOP' redefined <br>/usr/include/sys/termios.h:300: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:104: warning: `FLUSHO' redefined <br>/usr/include/sys/termios.h:307: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:110: warning: `PENDIN' redefined <br>/usr/include/sys/termios.h:308: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:112: warning: `NOFLSH' redefined <br>/usr/include/sys/termios.h:299: warning: this is the location of the previous definition <br>In file included from /home/work/apcupsd-3.14.4/include/apc.h:92, <br>                 from apcevents.c:25: <br>/usr/include/sys/ioctl.h:68: warning: `ECHO' redefined <br>/usr/include/sys/termios.h:295: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:75: warning: `NL0' redefined <br>/usr/include/sys/termios.h:219: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:76: warning: `NL1' redefined <br>/usr/include/sys/termios.h:220: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:80: warning: `TAB0' redefined <br>/usr/include/sys/termios.h:227: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:81: warning: `TAB1' redefined <br>/usr/include/sys/termios.h:228: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:82: warning: `TAB2' redefined <br>/usr/include/sys/termios.h:229: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:83: warning: `XTABS' redefined <br>/usr/include/sys/termios.h:234: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:85: warning: `CR0' redefined <br>/usr/include/sys/termios.h:222: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:86: warning: `CR1' redefined <br>/usr/include/sys/termios.h:223: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:87: warning: `CR2' redefined <br>/usr/include/sys/termios.h:224: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:88: warning: `CR3' redefined <br>/usr/include/sys/termios.h:225: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:90: warning: `FF0' redefined <br>/usr/include/sys/termios.h:245: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:91: warning: `FF1' redefined <br>/usr/include/sys/termios.h:246: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:93: warning: `BS0' redefined <br>/usr/include/sys/termios.h:239: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:94: warning: `BS1' redefined <br>/usr/include/sys/termios.h:240: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:103: warning: `TOSTOP' redefined <br>/usr/include/sys/termios.h:300: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:104: warning: `FLUSHO' redefined <br>/usr/include/sys/termios.h:307: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:110: warning: `PENDIN' redefined <br>/usr/include/sys/termios.h:308: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:112: warning: `NOFLSH' redefined <br>/usr/include/sys/termios.h:299: warning: this is the location of the previous definition <br>  CXX   src/lib/apcexec.c <br>In file included from /home/work/apcupsd-3.14.4/include/apc.h:92, <br>                 from apcexec.c:27: <br>/usr/include/sys/ioctl.h:68: warning: `ECHO' redefined <br>/usr/include/sys/termios.h:295: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:75: warning: `NL0' redefined <br>/usr/include/sys/termios.h:219: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:76: warning: `NL1' redefined <br>/usr/include/sys/termios.h:220: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:80: warning: `TAB0' redefined <br>/usr/include/sys/termios.h:227: warning: this is the location of the previous definition <br>/usr/include/sys/ioctl.h:81: warning: `TAB1' redefined <br>/usr/include/sys/termios.h:228: warning: t