Re: [Astlinux-devel] bug in UPS init.?

[Lonnie A. <li...@lo...>]

Hi David,

Years ago I wanted to disable the beeper on a Tripp-Lite UPS, below are the steps I used.  Possibly it might help you.  Step 1 was key.


1) Edit /etc/ups/upsd.users and add the lines:
--
[admin]
password = pass
instcmds = all
--

2) Apply the change without rebuilding the config files.
--
service ups restart
--

3) List what commands are available
--
upscmd -l ups
--

4) In this case "beeper.disable" was the desired command
--
upscmd -u admin -p pass ups beeper.disable
--

5)  Display UPS responses
--
upsc ups
--

6) Restart "ups" rebuilding the config files.
--
service ups stop
service ups init
--


Lonnie


> On Aug 5, 2020, at 8:18 PM, David Kerr <Da...@Ke...> wrote:
> 
> As I prepare to enjoy multiple days without power or internet I have been trying to reconfigure my UPS as it is sending LOWBATT far too early.  I tried to use upsrw command to set values into the UPS but kept getting...
> 
> Unexpected response from upsd: ERR ACCESS-DENIED
> 
> Even after editing upsd.user file.  After which I would do a 
> service ups init
> Well it turns out that is not good enough.  It regenerates all the config files but it does not reload the new config files.  It has to be followed by a
> service ups restart
> 
> Or... the init script could do a stop before the init?
> Or... the init script could send a reload to upsd?
> 
> Thanks
> David
> 
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel