Re: a question about apcupsd

I think I found the culprit.

sheliak# apcaccess status
<snip>
DSHUTD   : 020 Seconds
<snip>

20 seconds is probably not enough for my old Sparc.

Looking at the eeprom I have
sheliak# apcaccess eeprom

Valid EPROM values for the SMART-UPS 700 RM

                         Config        Current  Permitted
Description              Directive     Value    Values
===================================================================
Upper transfer voltage   HITRANSFER    253      253 264 271 280
Lower transfer voltage   LOTRANSFER    196      196 188 208 204
Return threshold         RETURNCHARGE  0        00 15 50 90
Output voltage on batts  OUTPUTVOLTS   230      230 240 220 225
Sensitivity              SENSITIVITY   H        H M L L
Low battery warning      LOWBATT       2        02 05 07 10
Shutdown grace delay     SLEEP         20       020 180 300 600
Alarm delay              BEEPSTATE     0        0 T L N
Wakeup delay             WAKEUP        0        000 060 180 300
Self test interval       SELFTEST      OFF      336 168 ON  OFF

I tried to change the sleep value with
sheliak# apcupsd --configure SLEEP 180
Attempting to configure UPS ...

Reading updated UPS configuration ...

<snip>
DSHUTD   : 020 Seconds
<snip>

Does it come from apcupsd or is it my UPS which doesn't allow eeprom changes?

Does someone have a workaround?

Regards,
Thierry.

On Wednesday 08 November 2006 14:43, Thierry Lacoste wrote:
> I'm running NetBSD 3.0 on a Sparc Ultra1 that I want to protect
> with an APC UPS.
> I installed and configured apcupsd-3.8.6nb5 then made some tests.
>
> When I unplug the serial cable I have the following message:
> Serial communications with UPS lost.
> When I plug it I have:
> Serial communications with UPS restored.
>
> When I unplug and plug the power cable on the APC I also have
> the expected messages.
>
> Now for the last test I put "TIMEOUT 60" in apcupsd.conf and
> restart apcupsd then I unplug the APC power cable and wait
> about 1 minute.
> The computer initiates a system shutdown but apparently
> it also shuts down the APC too early and the filesystems
> are not properly unmounted.
> Indeed when I restart the computer I have a long fsck.
>
> I have some i386 machines under FreeBSD 6.1 in a similar setting
> and never experienced this problem.
>
> What did I miss?
>
> Regards,
> Thierry.