Desc: Frequently Asked Questions
File: FAQ
Date: 7 December 2002
Auth: Russell Kroll <rkroll@exploits.org>

-----------------------------------------------------------------------------

 Q: I just upgraded, and ...

 A: You have read UPGRADING in the base directory of the distribution,
    right?  If not, go read it now, then come back to this file.

-----------------------------------------------------------------------------

 Q: upsstats says "Error: can't open template file (upsstats.html)".
    How do I fix this?

 A: Go into your CONFPATH and copy the sample template files over to
    their real names.

-----------------------------------------------------------------------------

 Q: My favorite UPS driver disappeared.  What happened?

 A: That driver is old, and nobody converted it to the new style that
    can use ups.conf and upsdrvctl, so it was yanked after 0.45.5.
    That was back in March 2002.

    Short version: unless someone converts that driver, it will not
    appear in any future releases.  That's called progress.  This was
    done to get rid of a lot of old compatibility hacks in the code.
    It also unified the documentation, since everyone now runs
    upsdrvctl and uses ups.conf.

    Long version: main.c (the core of all new/converted drivers) was
    introduced in March 2001 during the 0.45.0 development cycle.
    Any driver that didn't get converted in the meantime probably hadn't
    been maintained in at least a year, which is dubious right there.

    To get that driver back into the current releases, you need to
    convert it yourself or get someone to do it for you.  This isn't
    very hard - look at skel.c and some of the smaller drivers
    (fentonups, among others) to see how it's done.  The basic idea is
    that you rip out main, rename a few functions to upsdrv_* where
    needed, and provide a few new ones to fill out the interface.
    That's it.  The hard part of decoding the protocol has already been
    done for you in the original driver.

    By the way, to find the old driver, get nut-0.45.5.tar.gz and look
    in the models directory.      

-----------------------------------------------------------------------------

 Q: What happened to my driver?

 A: These drivers were removed due to the situation described above
    and have not been converted yet:

     aeg, bestfort, engetron, ipt-anzen, mustekups, optiups, toshiba1500

 A: Some drivers were renamed as they were upgraded:

	0.45.x         current

	newpowercom -> powercom
	newvictron  -> victronups
	mgeups      -> mge-utalk
	upseyeux    -> microdowell
	multilink   -> liebert

-----------------------------------------------------------------------------

 Q: I just upgraded and now it won't talk to any of my systems that are
    still running an older version before 0.50.0. 

 A: Older versions of the software used port 3305, which was conflicting
    with an assignment for odette-ftp.  NUT now uses its official IANA  
    port number - 3493.  Until you get the other systems upgraded, put a
    :3305 on the host name to use the old port.

-----------------------------------------------------------------------------

 Q: My UPS driver program won't work.  I'm starting it as root, and root
    owns the device, so what's the problem?

 A: The drivers drop root privileges long before the serial port is
    opened.  You'll need to change the permissions on that port so that
    their new user id can access it.  Normally this is "nobody", but it 
    may be changed at compile-time by using configure --with-user.

    Read the error message.  If you have a permissions mismatch, then
    you'll see something like this:

	Network UPS Tools - APC Smart protocol driver 0.60 (1.1.7)
	This program is currently running as youruid (UID 1234)
	/dev/ttyS2 is owned by user root (UID 0), mode 0600
	Change the port name, or fix the permissions or ownership 
	of /dev/ttyS2 and try again.
	Unable to open /dev/ttyS2: Permission denied

    Now is a good time to point out that using "nobody" is a bad idea,
    since it's a hack for NFS access.  You should create a new role 
    account (perhaps called "ups" or "nut"), and use that instead.

    Also, scroll down to the "security domains" question to see an
    even better way of restricting privileged operations.  Neither the
    drivers nor upsd ever need root powers, and that answer tells you
    how to make it work.

-----------------------------------------------------------------------------

 Q: upsc, upsstats, and the other clients give me "access denied".  The
    serial port permissions are fine, so what gives?

 A: In this case, "access denied" means the access to upsd, not the
    serial port.  You're being denied since the system has not been
    permission to speak to upsd according to the access controls.

    The fix is to edit the upsd.conf to allow those hosts to do what they
    need.  Clients like upsc, upsmon, and the CGI programs need "monitor"
    level access to work.  upsmon also needs a user defined in upsd.users.

    If you are getting this error from the programs that request a login
    name or password (upsrw, upscmd, upsset.cgi), then make sure your
    account is properly defined in upsd.users.

    After editing the upsd config files, you can do 'upsd -c reload'
    or kill -HUP <pid of upsd> to make it reload the configuration
    without restarting the process.

-----------------------------------------------------------------------------

 Q: I have an APC Smart-UPS connected with a grey APC cable and it won't
    work.  The Back-UPS type in the genericups driver works but then I 
    don't get to use all the nifty features in there.  Why doesn't the 
    right driver work?

 A: The problem lies in your choice of cable.  APC's grey cables
    generally only do "dumb" signalling - very basic yes/no info about
    the battery and line status.  While that is sufficient to detect a
    low battery condition while on battery, you miss out on all the
    goodies that you paid for.

    Note that the 940-0095B happens to be a grey cable, but it is actually
    a dual mode cable and can be used in smart mode.  If you have
    this cable, you need to edit your ups.conf to look like this:

	[myups]
		driver = apcsmart
		port = /dev/whatever
		cable = 940-0095B

    This also applies for the newapc driver.

    All other grey cables from APC are assumed to be "dumb".

    If your grey cable isn't the 940-0095B, the solution is to dump that
    cable and find one that supports APC's "smart" signalling.  Typically
    these come with the UPS and are black.  If your smart cable has
    wandered off, one can be built rather easily with some connectors and
    cable - there's no fancy wiring or resistors.

    See this URL for a handy diagram:

    http://www.exploits.org/nut/library/cables/940-0024C.jpg

    That should give you a workable clone of APC's 940-0024C cable.
    There are simpler solutions involving 3 wires that work just fine
    too, but Powerchute won't find the loopback DTR-DCD and RTS-CTS and
    will be annoyed.  If you don't ever plan to use Powerchute, 3 wires
    (RxD, TxD, GND) are sufficient.

    It should also be noted that the genericups driver has no way to detect
    the UPS, so it will fire up quite happily if it can open the serial
    port.  Merely having it start up is not necessarily an indication
    of success.  You should start it and then check the status with upsc
    or similar to be sure that it's reading the hardware properly.

-----------------------------------------------------------------------------

 Q: Why isn't configure finding gd?

 A: The process of finding gd was recently replaced since it was failing
    in too many situations.  The new one allows you to specify all of
    the compiler flags that may be necessary to make it work.

    NOTE: gd 2.0.5 through 2.0.7 have a gdlib-config script that isn't
    usable.  If you upgrade to at least gd 2.0.8, configure will use
    it to find the right flags to make it compile and link properly.

    If you're stuck with an older version of gd, you can use it if you
    specify the flags manually.  Look in gd's Makefile for "LIBS=", 
    then use that value when you call configure:

	./configure --with-gd-libs="<whatever>" --with-cgi

    If you don't have gd's Makefile available for some reason, you're
    in for a lot of trial and error.  

-----------------------------------------------------------------------------

 Q: Why PNG?  You used to generate GIF bars with upsimage back in 1998
    or 1999...

 A: http://www.burnallgifs.org/

-----------------------------------------------------------------------------

 Q: What about Y2K compliance and this software?

 A: That's pretty much a moot point now, isn't it?

    No problems were reported.

    As for 2038, well, that's another story.

-----------------------------------------------------------------------------

  Q: Why doesn't upsd implement the functionality of upsmon?  I have to
     run THREE programs to monitor my UPS!

  A: I try to follow the "tool for the job" philosophy.  It may mean
     more programs running, but the flexibility you get is usually
     worth it.

     Yes, the machine with the UPS attached will generally have 3
     processes (driver, upsd, upsmon) running, but this design allows a
     much bigger setup.  Imagine a data room with a bunch of machines
     all drawing power from the same UPS.  The rest of them just run
     upsmon.

     Besides, if upsmon were rolled into upsd, upsd would get even
     bigger than it is now.  You'd have one less process, but the
     RAM consumption would be pretty close to now.

     See data-room.txt for more configuration ideas and explanations.

-----------------------------------------------------------------------------

  Q: Why doesn't upsmon send a SIGPWR signal to init so it can deal with
     power events?

  A: New versions of the init man page taken from the sysvinit package
     are saying that usage of SIGPWR is discouraged, since /dev/initctl 
     control channel is the preferred way of communication.

  A: The name of the game is portability.  Not everyone's init handles
     that kind of signalling gracefully.  What's more, some admins
     might want to do things differently even if they have that kind of
     init running.

     So, to be compatible, upsmon just invokes a shell command.  If you
     want to use init's SIGPWR stuff, just put the right "kill" line in
     a shell script and make upsmon call it.  Everyone wins.

-----------------------------------------------------------------------------

  Q: Why can't upsset read my upsset.passwd file?

  A: You have an old version of upsset installed, since the current
     version doesn't use that file.  Install a new version and then try
     it again.

     Be sure to secure your CGI directory as instructed in the
     upsset.conf.

-----------------------------------------------------------------------------

  Q: Why won't bestfort talk to my Best Fortress UPS?

  Q: Why won't bestups talk to my Best Fortress UPS?

  A: bestfort handles some older / "traditional" models that tend to be
     black.  bestups is designed around the somewhat newer "PhoenixTec"
     protocol that seems to be associated with beige units.  If one 
     driver doesn't work, try the other one.

     Note: bestfort was removed after 0.45.5 since it was an old style
     driver that was not converted.  See the top of this file for more
     information, including how to get it back in current versions.

  A: bestfortress is a relatively new driver for very old Best Fortress
     equipment.  It's not the same as the old bestfort driver.  There
     seem to be several revisions of this hardware with the same name,
     and they all have different protocols.

     The moral of the story is: if one driver doesn't work, try the
     other one.

-----------------------------------------------------------------------------

  Q: What's this about "data stale"?

  A: It means your UPS driver hasn't updated things in a little while.
     upsd refuses to serve up data that isn't fresh, so you get the
     errors about staleness.

     If this happens to you, make sure your driver is still running.
     Also look at the syslog.  Sometimes the driver loses the connection
     to the UPS, and that will also make the data go stale.

     Note: some slow machines have trouble keeping up with the serial 
     ports during periods of extreme load.  I have an old 486 that
     regularly flips between "stale" and "OK" while running backups.

     If this happens a lot, you might consider cranking up DEADTIME
     in the upsd.conf to suppress some of the warnings for shorter
     intervals.  Use caution when adjusting this number, since it
     directly affects how long you run on battery without knowing
     what's going on with the UPS.

-----------------------------------------------------------------------------

  Q: Why do upsc (or any of the client programs) say "no such variable"
     when I try to run them?

  A: Usually this means that upsd has no data available for that UPS.
     Check your ups.conf and make sure that you have defined entries
     that make sense for the driver(s) that you are running.

-----------------------------------------------------------------------------

  Q: My system has an ATX power supply.  It will power off just fine, but
     it doesn't turn back on.  What can I do to fix this?

  A: This depends on how clueful your motherboard manufacturer is, and
     isn't a matter of the OS.  You have to do one of the following
     things depending on what's supported:

     - Set a jumper on the motherboard that means "return after outage"

     - Set something in the BIOS that says "power up after power failure"

     - Hack the cable between the power supply and the motherboard to fool
       it into powering up whenever line power is present

     - Teach a monkey to watch the machine and press the power button
       when the outage is over.

       This might work, but it creates high produce bills.

     If you can't use one of the first two options, give the board to
     an enemy.  Let them worry about it.

-----------------------------------------------------------------------------

  Q: My PowerMac G4 won't power back up by itself after the UPS shuts
     down.  What can I do about this?

  A: This is about the same situation as the ATX question above, only
     worse.  Earlier Macs apparently supported a hack where you could
     cat some magic characters at /dev/adb to enable "server mode".
     This would instruct the system to reboot while unattended.

     From Usenet post <6boftzxz51.fsf@ecc-office.sp.cs.cmu.edu>:

	# Send packet over the ADB bus to the PowerMac CUDA chip
	# telling it to reboot automatically when power is restored
	# after a power failure.

     	cat /etc/local/autoboot.adb > /dev/adb

     autoboot.adb contains these three bytes (in hex):  01 13 01

     Unfortunately, the hardware has evolved and there is no good
     equivalent for this hack on today's systems.

     If you find out how to do this, please send me some mail, since
     this affects one of my systems and my stop-gap solution is getting
     cranky.

-----------------------------------------------------------------------------

  Q: I want to keep the drivers and upsd in their own security domains.
     How can this be accomplished?

  A: Using a few role accounts and a common group, you can limit access
     to resources such as the serial port(s) leading to the UPS
     hardware.

     This is just an example.  Change the values to suit your systems.

     Create a user called 'nutdev' and another called 'nutsrv'.  Put
     them both in a group called 'nut'.

     Change the owner of any serial ports that will be used to nutdev,
     and set the mode to 0600.  Then change the ownership of your state
     directory (usually /var/state/ups) to nutdev.nut.

     For my development system this yields the following /dev entries:

     0 crw-------   1 nutdev   tty        4,  64 Sep  3 17:11 /dev/ttyS0
     0 crw-------   1 nutdev   tty        4,  65 Sep  3 17:11 /dev/ttyS1

     Start the driver(s) with su, like so:

     # su nutdev -c "/usr/local/ups/bin/upsdrvctl start"

     The listing for /var/state/ups then looks like this:

     4 drwxr-x---   2 nutdev   nut          4096 Aug 20 18:37 .
     4 drwxr-xr-x   4 root     root         4096 May 14 21:20 ..
     4 -rw-r-----   1 nutdev   nut            44 Sep  3 17:10 apcsmart-ttyS0
     4 -rw-r-----   1 nutdev   nut            44 Sep  3 17:10 fentonups-ttyS1

     You may have to remove old state files first if you are changing to
     this security scheme from an older install.  The drivers will create
     new ones with the right ownership and modes.

     You will probably have to change the ownership of upsd.conf and 
     upsd.users since upsd will no longer start as root.  Once you get
     them changed over to being accessible by nutsrv, start upsd:

     # su nutsrv -c "/usr/local/ups/sbin/upsd"

     Check your syslog to be sure everything's happy, then be sure to
     update your startup scripts so it uses this procedure on your next
     boot.   

     *** Big fat warning: if you use this scheme, you HAVE to use it
         every time you start the programs.  This goes for startup and
         shutdown.  Every time you call upsdrvctl, you have to do the
         "su user -c ..." scheme to make sure it starts as the correct
         user. 

         Don't forget to edit your shutdown scripts.  If the driver
         can't open the port, your UPS won't be able to power off at
         the end of the sequence.

         su nutdev -c "/usr/local/ups/bin/upsdrvctl shutdown"

-----------------------------------------------------------------------------

  Q: What's the point of that 'security domains' concept above?

  A: The point is limiting your losses.  If someone should happen to
     break into upsd in that environment, they should only gain access
     to that one user account.  Direct access to the serial device is
     not possible, since that is owned by another user.

     It also has the nice side effect that the drivers and upsd *never*
     have root permissions, even when started at boot-time.  Since they
     don't need it, there is no reason to let them have it, even 
     briefly. 

     There is also the possibility of running the drivers and upsd in a
     chroot jail.  See the chroot.txt provided in the source 
     distribution for an example implementation. 

     Why give would-be vandals any sort of help?

     Put it this way - I *wrote* good chunks of this stuff, and I still
     run the programs this way locally.  You should definitely consider
     using this technique.

-----------------------------------------------------------------------------

  Q: How can I make upsmon shut down my system after some fixed interval?

  A: You probably don't want to do this, since it doesn't maximize your
     runtime on battery.  Assuming you have a good reason for it (see
     the next entry), then look at upssched.txt or the upssched man
     page for some ideas.

-----------------------------------------------------------------------------

  Q: Why doesn't upsmon shut down my system?  I pulled the plug and nothing
     happened.

  A: Wait.  upsmon doesn't consider a UPS to be critical until it's both
     'on battery' and 'low battery' at the same time.  This is by design.
     Nearly every UPS supports the notion of detecting the low battery
     all by itself.  When the voltage drops below a certain point, it
     _will_ let you know about it.

     If your system has a really complicated shutdown procedure, you
     might need to shut down before the UPS raises the low battery flag.
     For most users, however, the default behavior is adequate.

     Ask yourself this: why buy a nice big UPS with the matching battery
     and corresponding runtime and then shutdown early?  If anything, I'd
     rather have a few more minutes running on battery during which the
     power might return.  Once the power's back, it's business as usual
     with no visible interruption in service.

     If you purposely shut down early, you guarantee an interruption in
     service by bringing down the box.

     See upssched.txt for information on how you can shutdown early if
     this is what you really want to do.

-----------------------------------------------------------------------------

  Q: The CGI programs report "access to that host is not authorized" - 
     what's going on?

  A: Those programs need to see a host in your hosts.conf before they
     will attempt communications.  This keeps people from feeding it
     random data to the programs and annoying others via your system.

     If your hosts.conf turns out to be configured correctly with 
     MONITOR entries and all that, check the permissions.  Your web
     server may be running the CGI programs as a user that can't read
     the file.

-----------------------------------------------------------------------------

  Q: Why does upsd complain about "shmctl failed: permission denied"?

  A: If you're using the 'security domains' startup method with su -c
     (see above), then you always have to start upsd in that way after
     that point.

     Otherwise, upsd starts as root, then switches to whatever was 
     compiled in (typically 'nobody') and that usually doesn't belong
     to the right group, so you can't get to the shared memory struct.

     This is only an issue when using shared memory mode.  Most systems
     actually mmap() the state file, and will never see this problem.

-----------------------------------------------------------------------------

  Q: upsd is running, so why can't I connect to it?

  A: Assuming you haven't changed the port on the command line or at
     compile-time, then you probably have some sort of firewall blocking
     the connection.

     When securing port 3493, remember that upsd runs both TCP and UDP
     listeners.

-----------------------------------------------------------------------------

  Q: How do you make upsmon reload the config file?

  Q: How do you make upsd reload the config file?

  A: Either find the pid of the background process and send it a SIGHUP,
     or just start it again with '-c reload'.

     Note: if signalling upsmon manually, make sure you hit the 
     unprivileged process and not the one running as root.  When in
     doubt, read the pid file - upsd.pid or upsmon.pid.

-----------------------------------------------------------------------------

  Q: I just bought a new WhizBang UPS that has a USB connector.  How do
     I monitor it?

  A: If you're using a very new version of Linux that has hiddev support
     or just happen to have the hiddev patches applied and working, you're
     in luck.  On any other system or an older Linux kernel, there's
     nothing for you just yet.

     CONFIG_USB_HIDDEV has finally appeared as a real configuration
     option in Linux 2.4.13.  Any version after this one, including the
     2.5 series, should also have it available.

     First you need to point configure at your hiddev.h file.  If it
     happens to be in /usr/src/linux/include/linux/hiddev.h, then you
     don't need to do anything.  Otherwise, use --with-linux-hiddev=PATH
     and set it right.

     hidups is not built by default, so call configure with 
     "--with-drivers=hidups" or go into your drivers directory and do
     "make hidups" by hand.

     Next, create an entry in ups.conf like this:

	[myups]
		driver = hidups
		port = /dev/usb/hid/hiddev0

     Use the right port that happens to apply to your hardware.  Yes,
     we know that USB is hotpluggable.  Yes, we know that things move
     around.  That's one of many reasons this is still tagged
     experimental.

     If you don't have those entries in /dev, make them with mknod -
     they're character devices, major 180, minor 96 and up.

     Once that's done, try starting it with upsdrvctl.

     Remember: this is brand new *experimental* software and is probably
     very broken.  Do us a favor and report successes or failures to
     the mailing lists.  You might also want to subscribe to the hidups
     list at lists.exploits.org to track development activity for this
     hardware.

     Developers on other systems (the BSDs in particular) are encouraged
     to pitch in to make this work on their kernel's USB implementation.

-----------------------------------------------------------------------------

  Q: Why isn't Linux seeing my USB UPS?

  A: Some USB UPS equipment needs a few non-default options in your
     kernel.  One of them is CONFIG_USB_LONG_TIMEOUT - try using this
     if you have a MGE Ellipse that isn't being recognized.

     Note: while CONFIG_USB_LARGE_CONFIG is in 2.4.18's Configure.help
     and looks like the answer to APC UPS troubles, it doesn't actually
     do anything.  You still have to mangle the config request code
     yourself.

-----------------------------------------------------------------------------

  Q: Why doesn't my package work?

  Q: I can't run this because there's no package for it.  Why isn't this
     in a package yet?

  A: Sorry, can't help you there.  The official releases are strictly
     source code, as posted on http://www.exploits.org/nut/.   If you 
     have an issue related to packaging, you need to talk to whoever
     built it for you.

-----------------------------------------------------------------------------

  Q: Why are there two copies of upsmon running?

  A: It's not really two complete copies if your OS forks efficiently.

     By default, upsmon runs most of the grunt work as an unprivileged
     user and keeps a stub process around with root powers that can
     only shut down the system when necessary.  This should make it much
     harder to gain root in the event a hole is ever discovered in
     upsmon.

     If this really bothers you and you like running lots of code as
     root, start upsmon with -p and it will go back to being one big
     process.

-----------------------------------------------------------------------------

  Q: When I tell upsd to reload the config files, it complains in the
     syslog that it can't open the upsd.conf.  It read the files
     when it started up, so why is it failing now?

  A: Look at who upsd is running as now - use 'ps'.  You'll probably see
     "nobody" in that first column, even though you started it as root.
     This is intentional - upsd drops root shortly after it starts up,
     but _after_ it gets done reading your config files.

     This means it can read the files once, but it can't reload them.
     This is a compromise to provide a better default environment for
     people who don't create a separate user for upsd.  The alternative
     would be running upsd as root, and that's just asking for trouble.

     If you want the reloading feature to work, the user that upsd
     runs as must be able to open the various config files.  You should
     create a user just for upsd, then make it own both of those config
     files.  See the "security domains" question above for a good
     way to do this.

     Note: upsd.conf and upsd.users should not be writable by this user.
     
     *** NEVER make upsd.conf or upsd.users world readable or writable.

     *** NEVER make upsd.conf or upsd.users accessible by "nobody".

     If you do either of these things and someone breaks into your
     system or starts messing with your UPS hardware, don't come crying
     to me or anyone else associated with this project.  You will have
     only yourself to blame.

-----------------------------------------------------------------------------

  Q: I have <some problem> with <some old version> ...

  A: Get the latest stable release, and see if it still happens.  If it
     goes away, it means someone else reported it and got it fixed a 
     long time ago.

     If that doesn't work, try the latest development version.

     If your problem is STILL there, then contact the mailing lists.

-----------------------------------------------------------------------------

  Q: Do you have to use a serial connection to monitor the UPS?
     What about direct network connections (SNMP or otherwise)?

  A: Right now, the only non-serial drivers are hidups, snmp-ups and
     powernet.  All three are experimental, which means they might not
     work properly in all situations.  hidups in particular only builds
     and runs on Linux as it is designed around the hiddev interface.

     Any time there is a gap in features, it's usually because the
     group of people who own that hardware and the group of people who
     write code don't overlap.  The fix is to make them overlap -
     turn an owner into a developer or vice-versa.

-----------------------------------------------------------------------------

  Q: What happened to the patch I sent?

  A: If a release goes by and your patch hasn't been included, it was
     probably dropped.  There can be a lot of patches waiting for 
     inclusion at some points, and occasionally some have to be
     rejected.

     Design issues or severe coding style problems can be the reason
     for this.  I try to point out what the problems are, but there are
     limits.  See developers.txt for some pointers on submitting
     patches.

     Sometimes patches are put on hold due to a feature freeze.  If it
     doesn't show up once the new version opens up, send it again.

-----------------------------------------------------------------------------

  Q: I'm not much of a programmer.  How can I help?

  A: There's always work to be done outside of the realm of code bashing.
     Documentation might not always be so clear.  A user's perspective
     is sometimes needed to appreciate this.

     Fielding questions on the mailing lists is also helpful.  This
     lets other people to focus on coding issues while allowing the
     original poster to get some information at the same time.  It's
     quite a relief to open that mailbox and find that someone else
     has already handled it successfully.

-----------------------------------------------------------------------------

  Q: I replaced the battery in my APC Smart-UPS and now it thinks the 
     battery is low all the time.  How do you fix this?

  Q: My APC UPS keeps reporting "OL LB", even after it's been charging
     for many hours.  What can I do about this?

  A: This happened to me, and some other people too.  The combination of
     our experiences should prove useful to you.

     First, you need to realize that the UPS apparently stores data about
     the battery, load, and runtime.  After replacing the battery, it
     needs to be clued in to the new situation.  If the traditional
     runtime calibration doesn't work, you have to try something a
     little more drastic.

     You need to *completely* drain the UPS while it has a good ground.
     This means you can't just pull the plug.  You also have to
     disconnect it from the computer so this software won't shut it
     down.

     The easiest way to do this is to first unplug your computer(s) from
     it, and plug in a token load like a lamp.  Also, move the UPS to a 
     power strip that doesn't switch the ground line or an outlet that
     you can switch off at your panel.

     Once the UPS is up at 100% charge (this is important), disconnect
     the power.  It _must_ remain connected to the ground, or the
     results may not be accurate.  Ignore the sounds it makes, and go
     away until it's done.  Don't do anything to the front panel while
     this is happening.

     After all of this, put things back the way they should be and let
     it charge up.  You should find that it again gives reasonable
     values and behavior, as it was when it was new.

     Thanks to Matthew Dharm for helping me nail down this procedure.

-----------------------------------------------------------------------------

  Q: multimon.cgi seems to be stuck at an old version, even though I
     just installed a new one.

  A: multimon was removed during the 1.1 development cycle.  upsstats
     now does everything it used to do, and then some.  You should just
     delete those files and start using upsstats directly.

-----------------------------------------------------------------------------

  Q: OK, I switched to upsstats.  Now it's giving me Celsius.  I like
     Fahrenheit.  Where's the config file to switch it back?

  A: Temperature scales are handled by the template files, so edit your
     upsstats.html and change it from TEMPC to TEMPF.

-----------------------------------------------------------------------------

  Q: Why is the mailing list ignoring me?

  A: You probably asked a question that's answered in this FAQ or
     somewhere else in the documentation and nobody wants to quote it
     for you.

     Convincing the other subscribers that you've actually read down this
     far might be useful.  You might mention "queequeg" for better results.

     This URL may also be helpful:

     	http://tuxedo.org/~esr/faqs/smart-questions.html

-----------------------------------------------------------------------------

  Q: How can you answer questions to situations that nobody's encountered
     yet?  Isn't this a frequently asked questions file?

  A: Magic.

  A: It's both that and a frequently *anticipated* questions file, too.

     The idea is to write it up in here so that nobody asks the mailing
     list when it finally does get released.  

-----------------------------------------------------------------------------
