I wrote:
>Stephen Harris wrote:
>> On Tue, Nov 06, 2012 at 04:56:20PM -0500, m.roth@xxxxxxxxx wrote:
>>> Anyone else around using apcupsd? I seem to be seeing a problem, and I'd
>
<snip>
>> apccontrol isn't flagged as a config file in the rpm
<snip>
>> The script says
>
>> # WARNING: the apccontrol file will be overwritten every time you
update your
>> # apcupsd, doing `make install'. Your own customized scripts will _not_ be
>> # overwritten. If you wish to make changes to this file (discouraged), you
>> # should change apccontrol.sh.in and then rerun the configure process.
>
>> If you can't change apcupsd.conf config to meet your needs then _don't_
>> change apccontrol; add a custom script that does an "exit 99" to prevent
>> the shutdown from running.
> It looks like you're right... EXCEPT that you missed the part about
changing
> apccontrol.sh.in, which appears to me to be something you get if you build
<snipo>
Ok, finally had time to go back and read carefully. And then, with a
little googling, saw someone else's reaction as the same as mine:
apccontrol has a *lot* of options. Does this mean that I need to write a
script names poweroff so that it doesn't shut down, *and* have symlinks to
that from loadlimit, runlimit, doreboot, onbattery, failing, and timeout?
If so, that's ugly....
mark
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
