User's Manual UPS control system

slave that is sufficiently short that you are sure that the slave will
shutdown before the master. If the shutdown is done with a poweroff,
this will also save power so that the master can stay up longer.
Q: How do I ensure that my database server is correctly shutdown?
A: You simply add whatever commands are necessary in the appropri-
ate case statements in /etc/apcupsd/apccontrol, which is a standard
script file that is called to actually do the shutdown. Alternatively,
you can add your own script file that will be called before doing the
commands in apccontrol. Your script file must have the same name as
the appropriate case statement in apccontrol; it must be executable;
and it must be in the same directory as apccontrol.
Q: I have Win2k Advanced server, and when starting the service, get:
Could not start the Apcupsd Server service on Local Computer. Error
1067: The process terminated unexpectedly
A: The most common error causing your problem is an incorrect serial port
specification on your DEVICE directive. It should be:
DEVICE /dev/com2
On WinNT machines, and probably Win2000 machines you MUST
use /dev/com2 unless you modify the behavior of the boot process to
prevent Windows from probing the port. This is documented in our
manual for WinNT. Although I imagine it is the same for Win2000, I
am not sure.
The second most common problem is bad placement of the files i.e.
you did not install them in c:\apcupsd Unfortunately for the current
release, this path is “hard coded” into the binaries.
The third most common problem is that you did not run the setup.bat
script after loading the files. This is necessary to install apcupsd as a
service.
If all the above fails, try starting apcupsd by hand inside a CYGWIN
rxvt window if you use an rxvt window rather than a DOS window,
you will see many more of the error messages.
In addition, most of the apcupsd startup errors are reported in:
c:\apcupsd\etc\apcupsd\apcupsd.events
Many error messages associated with Windows services will be re-
ported in the Windows System Log.
99