# Network UPS Tools: example upsmon configuration
#
# This file contains passwords, so keep it secure.


# --------------------------------------------------------------------------
# RUN_AS_USER <userid>
#
# By default, upsmon splits into two processes.  One stays as root and
# waits to run the SHUTDOWNCMD.  The other one switches to another userid
# and does everything else.
#
# The default nonprivileged user is set at compile-time with
# 	'configure --with-user=...'.
#
# You can override it with '-u <user>' when starting upsmon, or just
# define it here for convenience.
#
# Note: if you plan to use the reload feature, this file (upsmon.conf)
# must be readable by this user!  Since it contains passwords, DO NOT
# make it world-readable.  Also, do not make it writable by the upsmon
# user, since it creates an opportunity for an attack by changing the
# SHUTDOWNCMD to something malicious.
#
# For best results, you should create a new normal user like "nutmon",
# and make it a member of a "nut" group or similar.  Then specify it
# here and grant read access to the upsmon.conf for that group.
#
# This user should not have write access to upsmon.conf.
#
# RUN_AS_USER nutmon


RUN_AS_USER admin


# --------------------------------------------------------------------------
# MONITOR <system> <powervalue> <username> <password> ("master"|"slave")
#
# List systems you want to monitor.  Not all of these may supply power
# to the system running upsmon, but if you want to watch it, it has to
# be in this section.
#
# You must have at least one of these declared.
#
# <system> is a UPS identifier in the form <upsname>@<hostname>[:<port>]
# like ups@localhost, su700@mybox, etc.
#
# Examples:
#
#  - "su700@mybox" means a UPS called "su700" on a system called "mybox"
#
#  - "fenton@bigbox:5678" is a UPS called "fenton" on a system called
#    "bigbox" which runs upsd on port "5678".
#
# The UPS names like "su700" and "fenton" are set in your ups.conf
# in [brackets] which identify a section for a particular driver.
#
# If the ups.conf on host "doghouse" has a section called "snoopy", the
# identifier for it would be "snoopy@doghouse".
#
# <powervalue> is an integer - the number of power supplies that this UPS
# feeds on this system.  Most computers only have one power supply, so this
# is normally set to 1.  You need a pretty big or special box to have any
# other value here.
#
# You can also set this to 0 for a system that doesn't supply any power,
# but you still want to monitor.  Use this when you want to hear about
# changes for a given UPS without shutting down when it goes critical,
# unless <powervalue> is 0.
#
# <username> and <password> must match an entry in that system's
# upsd.users.  If your username is "monmaster" and your password is
# "blah", the upsd.users would look like this:
#
#	[monmaster]
#		password  = blah
#		allowfrom = 	(whatever applies to this host)
#		upsmon master 	(or slave)
#
# "master" means this system will shutdown last, allowing the slaves
# time to shutdown first.
#
# "slave" means this system shuts down immediately when power goes critical.
#
# Examples:
#
# MONITOR myups@bigserver 1 monmaster blah master
# MONITOR [email='su700@server.example.com'][/email] 1 upsmon secretpass slave


MONITOR qnapups@0.0.0.0 1 admin 123456 slave


# --------------------------------------------------------------------------
# MINSUPPLIES <num>
#
# Give the number of power supplies that must be receiving power to keep
# this system running.  Most systems have one power supply, so you would
# put "1" in this field.
#
# Large/expensive server type systems usually have more, and can run with
# a few missing.  The HP NetServer LH4 can run with 2 out of 4, for example,
# so you'd set that to 2.  The idea is to keep the box running as long
# as possible, right?
#
# Obviously you have to put the redundant supplies on different UPS circuits
# for this to make sense!  See big-servers.txt in the docs subdirectory
# for more information and ideas on how to use this feature.


MINSUPPLIES 1


# --------------------------------------------------------------------------
# SHUTDOWNCMD "<command>"
#
# upsmon runs this command when the system needs to be brought down.
#
# This should work just about everywhere ... if it doesn't, well, change it.


SHUTDOWNCMD "/sbin/shutdown -h +0"

#!/bin/sh


#### modify /etc/init.d/udev_run.sh
# add Vendor 0403 - Product 6001 to blacklist (not required)
# sed -i 's/not_ups_vid_list=(1d6b 05e3 046d 1005 0b05 1c05 1c05 03f0)/not_ups_vid_list=(1d6b 05e3 046d 1005 0b05 1c05 1c05 03f0 0403)/g' /etc/init.d/udev_run.sh
# sed -i 's/not_ups_pid_list=(xxxx 0608 0826 b155 17ba 3074 2074 e207)/not_ups_pid_list=(xxxx 0608 0826 b155 17ba 3074 2074 e207 6001)/g' /etc/init.d/udev_run.sh


# disable ups_yec daemon
sed -i 's/\/sbin\/daemon_mgr ups_yec start "\/sbin\/ups_yec &"/#\/sbin\/daemon_mgr ups_yec start "\/sbin\/ups_yec &"/g' /etc/init.d/udev_run.sh


# disable UPS in config (seems to be the magic switch)
/sbin/setcfg UPS ENABLE FALSE


# remove ups_yec
/sbin/daemon_mgr ups_yec stop "/sbin/ups_yec &"
rm /tmp/ups_temp
echo '#!/bin/sh' > /sbin/ups_yec