>народ... ну момогите кто-нить справиться с этой бедой.... нужно чтобы сервер выключался
>через 5 мин после падения питания, или хотябы просто выключался после
>падения питалова
вот тебе мой конфиг, который успешно управляет двумя серверами (второй по сети - lan в смыле :-)).
PS - выключается через 15 мин., где править - ты знаешь.
## apcupsd.conf v1.1 ##
#
# for apcupsd release 3.8.5 freebsd
#
# "apcupsd" POSIX config file
#
# If you have used a prior version of apcupsd, the CONTROL script file
# (/sbin/powersc) has now been replaced by /etc/apcupsd/apccontrol.
# Consequently, the CONTROL configuration statement is obsolete.
# The following configuration statements have been replaced by scripts
# called from /etc/apcupsd/apccontrol, and thus are obsolete:
# BATTCMD, LIMITCMN, LOADCMD, PWRCMD, REBOOTCMD, REMOTECMD, RETCMD,
# and TIMECMD.
#
#
#
# ========= General configuration parameters ============
#
# UPSCABLE [ simple | smart |
# 940-00(20B,23A,24B,24C,24G,95A,95B,95C) |
# 940-15(24C) |
# ether ]
# defines the type of cable that you have.
UPSCABLE smart
#
# UPSTYPE [ backups | sharebasic | netups |
# backupspro | smartvsups |
# newbackupspro | backupspropnp |
# smartups | matrixups | sharesmart ]
# defines the type of UPS you have.
UPSTYPE smartups
#
#
#DEVICE <string> /dev/<serial port>
# name of your serial port
DEVICE /dev/cuaa0
#
#LOCKFILE <path to lockfile>
# path for serial port lock file
LOCKFILE /var/spool/lock
#
#
#
# ======== configuration parameters used during power failures ==========
#
# 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 1
#
#
# 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 900
#
#
# 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 set, 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 the 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).
NETSERVER on
#
# NISPORT <port> default is 7000
# 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 7000
#
# If you want the last few EVENTS to be available over the network
# by the network information server, you must define an EVENTSFILE.
# Only the last 50 or so events are kept.
EVENTSFILE /var/log/apcupsd.events
#
#
#
#
# ===== 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 local0
#
#
#
#
# ========== Configuration statements used in updating the UPS EPROM =========
#
# UPS name, max 8 characters -- used only during -n or --rename-ups
UPSNAME UPS_IDEN
#
# Battery date - 8 characters -- used only during -u or --update-battery-date
#BATTDATE mm/dd/yy
#
# The following items are set during -c or --configure
#
# 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
#
#
#
# ========== 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. Obviously, the master is connected
# to the UPS via the serial cable, and it communicates to the
# "slaves" via the network -- i.e. the slaves get their info
# concerning the UPS via the ethernet.
#
# UPSCLASS [ standalone | shareslave | sharemaster | netslave | netmaster ]
# normally standalone unless you share a UPS with multiple machines.
UPSCLASS netmaster
#
# Unless you want to share the UPS (power multiple machines).
# this should be disable
# UPSMODE [ disable | share | net | sharenet ]
UPSMODE net
#
#NETACCESS <string> [ true | false ] Enable Network Access Support
NETACCESS true
#
# NETTIME <int>
NETTIME 10
#
# NETPORT <int>
NETPORT 6666
#
# MASTER <string>
#MASTER
#
# SLAVE <string>
SLAVE ra
#
# USERMAGIC <string>
#USERMAGIC
#
Вариант для распечатки
OpenNET: Виртуальная конференция (Public)
(??) on
22-Июл-04, 12:21 (MSK)
