config apcupsd for Slackware?

So I've installed apcupsd for Slackware and I am reading thru the documentation at:

http://www.apcupsd.com/manual/USB_Co...00000000000000

Which talks about setting up hiddenV under either /dev or /dev/usb. The documentation also talks about running a script to do that, but I don't see that under /etcapcupsd.

Does anyone know what my next step is?

It's been awhile since I set this up, but I believe there should be a script called make-hiddev in the example directory, this should solve that step for ya.

I looked to a script to make the files under /dev, but I don't see them...this is what I currently have under /etc/apcupsd.conf

cmmiller@darkstar:/etc/apcupsd$ ls -a
./ apccontrol* apcupsd.conf.new changeme* commok* masterconnect* multimon.conf onbattery*
../ apcupsd.conf apcupsd.css commfailure* hosts.conf mastertimeout* offbattery*

Also I went thru the apcupsd.conf file and made a few changes

## apcupsd.conf v1.1 ##
# 
#  for apcupsd release 3.12.3 (26 April 2006) - slackware
#
# "apcupsd" POSIX config file

#
# ========= General configuration parameters ============
#

# UPSNAME xxx
#   Use this to give your UPS a name in log files and such. This
#   is particulary useful if you have multiple UPSes. This does not
#   set the EEPROM. It should be 8 characters or less.
#UPSNAME

# UPSCABLE <cable>
#   Defines the type of cable connecting the UPS to your computer.
#
#   Possible generic choices for <cable> are:
#     simple, smart, ether, usb
#
#   Or a specific cable model number may be used:
#     940-0119A, 940-0127A, 940-0128A, 940-0020B,
#     940-0020C, 940-0023A, 940-0024B, 940-0024C,
#     940-1524C, 940-0024G, 940-0095A, 940-0095B,
#     940-0095C, M-04-02-2000
#
# Changed June 17th 2006 from smart to usb
# UPSCABLE smart
UPSCABLE usb 

# To get apcupsd to work, in addition to defining the cable
# above, you must also define a UPSTYPE, which corresponds to
# the type of UPS you have (see the Description for more details).
# You must also specify a DEVICE, sometimes referred to as a port.
# For USB UPSes, please leave the DEVICE directive blank. For
# other UPS types, you must specify an appropriate port or address.
#
# UPSTYPE   DEVICE           Description
# apcsmart  /dev/tty**       Newer serial character device,
#                            appropriate for SmartUPS models using
#                            a serial cable (not USB).
#
# usb       <BLANK>          Most new UPSes are USB.
#                            A blank DEVICE setting enables
#                            autodetection, which is th best choice
#                            for most installations.
#
# net       hostname:port    Network link to a master apcupsd
#                            through apcupsd's Network Information
#                            Server. This is used if you don't have
#                            a UPS directly connected to your computer.
#
# snmp      hostname:port:vendor:community
#                            SNMP Network link to an SNMP-enabled
#                            UPS device. Vendor is the MIB used by
#                            the UPS device: can be "APC", "APC_NOTRAP"
#                            or "RFC" where APC is the powernet MIB,
#                            "APC_NOTRAP" is powernet with SNMP trap
#                            catching disabled, and RFC is the IETF's 
#                            rfc1628 UPS-MIB. Port is usually 161. 
#                            Community is "private".
#
# dumb      /dev/tty**       Old serial character device for use 
#                            with simple-signaling UPSes.
#
UPSTYPE usb
# Comment out on June 17th 2006
# DEVICE /dev/ttyS0


# LOCKFILE <path to lockfile>
#   Path for device lock file.
LOCKFILE /var/lock

#
# ======== Configuration parameters used during power failures ==========
#

# The ONBATTERYDELAY is the time in seconds from when a power failure
#   is detected until we react to it with an onbattery event.
#
#   This means that, apccontrol will be called with the powerout argument
#   immediately when a power failure is detected.  However, the
#   onbattery argument is passed to apccontrol only after the 
#   ONBATTERYDELAY time.  If you don't want to be annoyed by short
#   powerfailures, make sure that apccontrol powerout does nothing
#   i.e. comment out the wall.
ONBATTERYDELAY 6

# 
# Note: BATTERYLEVEL, MINUTES, and TIMEOUT work in conjunction, so
# the first that occurs will cause the initation of a shutdown.
#

# If during a power failure, the remaining battery percentage
# (as reported by the UPS) is below or equal to BATTERYLEVEL, 
# apcupsd will initiate a system shutdown.
BATTERYLEVEL 5

# If during a power failure, the remaining runtime in minutes 
# (as calculated internally by the UPS) is below or equal to MINUTES,
# apcupsd, will initiate a system shutdown.
MINUTES 3

# If during a power failure, the UPS has run on batteries for TIMEOUT
# many seconds or longer, apcupsd will initiate a system shutdown.
# A value of 0 disables this timer.
#
#  Note, if you have a Smart UPS, you will most likely want to disable
#    this timer by setting it to zero. That way, you UPS will continue
#    on batteries until either the % charge remaing drops to or below BATTERYLEVEL,
#    or the remaining battery runtime drops to or below MINUTES.  Of course,
#    if you are testing, setting this to 60 causes a quick system shutdown
#    if you pull the power plug.   
#  If you have an older dumb UPS, you will want to set this to less than
#    the time you know you can run on batteries.
TIMEOUT 0

#  Time in seconds between annoying users to signoff prior to
#  system shutdown. 0 disables.
ANNOY 300

# Initial delay after power failure before warning users to get
# off the system.
ANNOYDELAY 60

# The condition which determines when users are prevented from
# logging in during a power failure.
# NOLOGON <string> [ disable | timeout | percent | minutes | always ]
NOLOGON disable

# If KILLDELAY is non-zero, apcupsd will continue running after a
# shutdown has been requested, and after the specified time in
# seconds attempt to kill the power. This is for use on systems
# where apcupsd cannot regain control after a shutdown.
# KILLDELAY <seconds>  0 disables
KILLDELAY 0

#
# ==== Configuration statements for Network Information Server ====
#

# NETSERVER [ on | off ] on enables, off disables the network
#  information server. If netstatus is on, a network information
#  server process will be started for serving the STATUS and
#  EVENT data over the network (used by CGI programs).
# changed June 17th 2006 
# NETSERVER on
NETSERVER off

# NISIP <dotted notation ip address>
#  IP address on which NIS server will listen for incoming connections.
#  Default value is 0.0.0.0 that means any incoming request will be
#  serviced but if you want it to listen to a single subnet you can
#  set it up to that subnet address, for example 192.168.10.0
#  Additionally you can listen for a single IP like 192.168.10.1
# Commented out June 17th 
# NISIP 0.0.0.0

# NISPORT <port> default is 3551 as registered with the IANA
#  port to use for sending STATUS and EVENTS data over the network.
#  It is not used unless NETSERVER is on. If you change this port,
#  you will need to change the corresponding value in the cgi directory
#  and rebuild the cgi programs.
# NISPORT 3551

# If you want the last few EVENTS to be available over the network
# by the network information server, you must define an EVENTSFILE.
# EVENTSFILE /var/log/apcupsd.events

# EVENTSFILEMAX <kilobytes>
#  By default, the size of the EVENTSFILE will be not be allowed to exceed
#  10 kilobytes.  When the file grows beyond this limit, older EVENTS will
#  be removed from the beginning of the file (first in first out).  The
#  parameter EVENTSFILEMAX can be set to a different kilobyte value, or set
#  to zero to allow the EVENTSFILE to grow without limit.
# comment out June 17th 2006
# EVENTSFILEMAX 10

#
# ========== Configuration statements used if sharing =============
#            a UPS and controlling it via the network              

# The configuration statements below are used if you want to share one 
# UPS to power multiple machines and have them communicate by the network.
# Most of these items are for Master/Slave mode only, however NETTIME is
# also used for Client/Server NIS networking with the net driver.

# NETTIME <int>
#   Interval (in seconds) at which the slave or client polls the master
#   or server. This is applicable to BOTH master/slave and client/server
#   (NIS) networking.
#NETTIME 100

#
# Remaining items are for Master/Slave networking ONLY
#

# UPSCLASS [ standalone | shareslave | sharemaster | netslave | netmaster ]
#   Normally standalone unless you share a UPS with multiple machines.
#   
UPSCLASS standalone

# UPSMODE [ disable | share | net | sharenet ]
#   Unless you want to share the UPS (power multiple machines),
#   this should be disable.
UPSMODE disable

# NETPORT <int>
#   Port on which master/slave networking communicates.
#NETPORT 6666

# MASTER <machine-name>
#   IP address of the master. Only applicable on slaves.
#MASTER

# SLAVE <machine-name>
#   IP address(es) of the slave(s). Only applicable on master.
#SLAVE slave1
#SLAVE slave2

# USERMAGIC <string>
#   Magic string use by slaves to identify themselves. Only applicable
#   on slaves.
#USERMAGIC

#
# ===== Configuration statements to control apcupsd system logging ========
#

# Time interval in seconds between writing the STATUS file; 0 disables
STATTIME 0

# Location of STATUS file (written to only if STATTIME is non-zero)
STATFILE /var/log/apcupsd.status

# LOGSTATS [ on | off ] on enables, off disables
# Note! This generates a lot of output, so if         
#       you turn this on, be sure that the
#       file defined in syslog.conf for LOG_NOTICE is a named pipe.
#  You probably do not want this on.
LOGSTATS off

# Time interval in seconds between writing the DATA records to
#   the log file. 0 disables.
DATATIME 0

# FACILITY defines the logging facility (class) for logging to syslog. 
#          If not specified, it defaults to "daemon". This is useful 
#          if you want to separate the data logged by apcupsd from other
#          programs.
#FACILITY DAEMON

#
# ========== Configuration statements used in updating the UPS EPROM =========
#

#
# These statements are used only by apctest when choosing "Set EEPROM with conf
# file values" from the EEPROM menu. THESE STATEMENTS HAVE NO EFFECT ON APCUPSD.
#

# UPS name, max 8 characters 
#UPSNAME UPS_IDEN

# Battery date - 8 characters
#BATTDATE mm/dd/yy

# Sensitivity to line voltage quality (H cause faster transfer to batteries)  
# SENSITIVITY H M L        (default = H)
#SENSITIVITY H

# UPS delay after power return (seconds)
# WAKEUP 000 060 180 300   (default = 0)
#WAKEUP 60

# UPS Grace period after request to power off (seconds)
# SLEEP 020 180 300 600    (default = 20)
#SLEEP 180

# Low line voltage causing transfer to batteries
# The permitted values depend on your model as defined by last letter 
#  of FIRMWARE or APCMODEL. Some representative values are:
#    D 106 103 100 097
#    M 177 172 168 182
#    A 092 090 088 086
#    I 208 204 200 196     (default = 0 => not valid)
#LOTRANSFER  208

# High line voltage causing transfer to batteries
# The permitted values depend on your model as defined by last letter 
#  of FIRMWARE or APCMODEL. Some representative values are:
#    D 127 130 133 136
#    M 229 234 239 224
#    A 108 110 112 114
#    I 253 257 261 265     (default = 0 => not valid)
#HITRANSFER 253

# Battery change needed to restore power
# RETURNCHARGE 00 15 50 90 (default = 15)
#RETURNCHARGE 15

# Alarm delay 
# 0 = zero delay after pwr fail, T = power fail + 30 sec, L = low battery, N = never
# BEEPSTATE 0 T L N        (default = 0)
#BEEPSTATE T

# Low battery warning delay in minutes
# LOWBATT 02 05 07 10      (default = 02)
#LOWBATT 2

# UPS Output voltage when running on batteries
# The permitted values depend on your model as defined by last letter 
#  of FIRMWARE or APCMODEL. Some representative values are:
#    D 115
#    M 208
#    A 100
#    I 230 240 220 225     (default = 0 => not valid)
#OUTPUTVOLTS 230

# Self test interval in hours 336=2 weeks, 168=1 week, ON=at power on
# SELFTEST 336 168 ON OFF  (default = 336)
#SELFTEST 336

Also, I wonder if I have to setup the apc under /mnt, since it is a device...?

I'll have to continue to read up on this, and will post more if I make more progress.

thanks

The make-hiddev script is in the examples directory in the directory where you untar'd everthing...that is if you compiled all this from the source code.

Originally Posted by buaku The make-hiddev script is in the examples directory in the directory where you untar'd everthing...that is if you compiled all this from the source code.

I used installpkg...which I got from
here

http://www.linuxpackages.net/search_...cupsd&ver=10.2

looks like it isn't there...

You could try downloading the source and just running that script.

Or you could remove the package and try installing it straight from source.

Originally Posted by buaku You could try downloading the source and just running that script. Or you could remove the package and try installing it straight from source.

***UPDATE***

I've removed the package and have installed from source.

Apcupsd is set to run at boot time and when I look at /proc/bus/usb,
here is the output

cmmiller@ladytron:/proc/bus/usb$ cat drivers
         usbdevfs
         hub
         usb-storage
 96-111: hiddev
         hid
cmmiller@ladytron:/proc/bus/usb$ cat devices
T:  Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12  MxCh= 4
B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0000 ProdID=0000 Rev= 0.00
S:  Product=USB OHCI Root Hub
S:  SerialNumber=e0a28000
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms
T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12  MxCh= 4
B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0000 ProdID=0000 Rev= 0.00
S:  Product=USB OHCI Root Hub
S:  SerialNumber=e0a26000
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms
T:  Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  2 Spd=1.5 MxCh= 0
D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=051d ProdID=0002 Rev= 1.06
S:  Manufacturer=APC
S:  Product=Back-UPS ES 350 FW:800.e5.D USB FW:e5
S:  SerialNumber=AB0446249686
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=00 Prot=00 Driver=hid
E:  Ad=81(I) Atr=03(Int.) MxPS=   6 Ivl=10ms
T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh= 8
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS= 8 #Cfgs=  1
P:  Vendor=0000 ProdID=0000 Rev= 2.04
S:  Manufacturer=Linux 2.4.31 ehci_hcd
S:  Product=PCI device 10de:00e8 (nVidia Corporation)
S:  SerialNumber=00:02.2
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=256ms

Under S:

S:  Manufacturer=APC
S:  Product=Back-UPS ES 350 FW:800.e5.D USB FW:e5

It detected my APC UPS, but when I rebooted, the apcupsd daemon doesn't show running in the background...

What do I need to do in order to get this set up and running
correctly?

thanks

It detected my APC UPS, but when I rebooted, the apcupsd daemon doesn't show running in the background...

Do you know when in your boot process the apcupsd daemon is started? If it is happening before the USB system is in place, that might cause the daemon to not start. On my rig, I'm calling rc.apcupsd on the first line of my rc.local and have had no problems with the daemon starting.

Originally Posted by Hangdog42 Do you know when in your boot process the apcupsd daemon is started? If it is happening before the USB system is in place, that might cause the daemon to not start. On my rig, I'm calling rc.apcupsd on the first line of my rc.local and have had no problems with the daemon starting.

I add the following to /etc/rc.d/rc.local

#12/11/2006 - Start APCUPSD on bootup
echo "Starting Power Management Daemon:"
./etc/rc.d/rc.apcupsd start | status

From here it throws out an error, but as root, I check it from /etc/rc.d

root@ladytron:/etc/rc.d# ./rc.apcupsd start
Starting apcupsd power management..  Already running.
root@ladytron:/etc/rc.d# ./rc.apcupsd status
FATAL ERROR in apcaccess.c at line 252
tcp_open: cannot connect to server localhost on port 3551.
ERR=Connection refused

Looks like I have to do some more work in order to get this to work...

thanks

Ok, so I put the apcupsd error into google and only got a few hits, there was one URL

http://www.webservertalk.com/archive...5-1524158.html

Where the guy, who is running Debian, is having the same problems as me, problem with his Linux and detecting usb devices...

http://www.linuxquestions.org/questi...ght=JockVSJock

Back to square one...I have no fucking clue on how to troubleshoot this...

Um, I don't know if this is part of the problem, but I just noticed this in your rc.local command:

./etc/rc.d/rc.apcupsd start | status

That . leading the command may be screwing things up if it is really there.

To be honest, you might want to take another run at this from the top. I read through the instructions you were following and I'm wondering if they are leading you off a bit. I used these instructions when I installed and haven't had many troubles. There are also http://ftp.slackbuilds.org/repository/system/apcupsd/ that may help.

Oh crap, ignore my previous post. It turns out my apcupsd hasn't been running since the upgrade to Slackware 11 due to changes in udev, and now that I've "fixed" the rules, apcupsd isn't finding the UPS.

Why would there be a problem with rc.apcupsd? Any file under /etc/rc.d had a dot with the name...

root@ladytron:/etc/rc.d# ls -a
./     rc.6*               rc.S*        rc.bind       rc.gpm*      rc.inet1.conf  rc.keymap*   rc.nfsd*      rc.scanluns*  rc.syslog*
../    rc.6.200612031551*  rc.acpid*    rc.cups*      rc.hotplug*  rc.inet2*      rc.local*    rc.portmap    rc.sendmail   rc.sysvinit*
rc.0@  rc.K*               rc.alsa*     rc.dnsmasq    rc.httpd*    rc.inetd*      rc.modules*  rc.rpc        rc.serial     rc.udev*
rc.4*  rc.M*               rc.apcupsd*  rc.font.new*  rc.inet1*    rc.ip_forward  rc.mysqld    rc.saslauthd  rc.sshd*

Let me know if you have any other ideas, I am open to anything at this time...

thanks

Why would there be a problem with rc.apcupsd? Any file under /etc/rc.d had a dot with the name...

My problem was the path difference in your rc.local file between this:

/etc/rc.d/rc.apcupsd start | status

and this:

./etc/rc.d/rc.apcupsd start | status

In the first case, no matter what the current directory is, /etc/rc.d/rc.apcupsd will be run. In the second case, /etc/rc.d/rc.apcupsd will run only if the current directory is /, otherwise it won't be found. I honestly don't know what the current directory is when rc.local is run, but I never assume one, I just give the full path.

Unfortunately I haven't had time to work on this but believe me, I'll post something when I figure it out.

Ok, I see it now...Hit me like a ton of bricks!!!

Remove the . from

./etc/rc.d/rc.apcupsd start | status

So it looks like

./etc/rc.d/rc.apcupsd start | status

thanks