Nut upsuser - Dec 2013 - upsrw: "Unexpected response from upsd: ERR READONLY"

After issuing this command:

/upsrw -s ups.delay.shutdown=180 -u admin -p mypassword myups

/I obtain this error:/

Unexpected response from upsd: ERR READONLY

/After issuing this command:/

upsrw myups

/I obtain no output./

/In my /upsd.users/ file I have these settings:

/[admin]//
//password = mypassword//
//actions = SET//
//instcmds = ALL//
//
//[myuser]//
//password = mypassword//
//allowfrom = localhost//
//upsmon master//
/
My nut version is/2.6.3 (Ubuntu 12.10)
/Drivers are/blazer_usb


/


/

/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20131216/1505ea8c/attachment.html>

On Dec 15, 2013, at 7:59 PM, Roberto Martelli wrote:
> Unexpected response from upsd: ERR READONLY
> 
> After issuing this command:
> 
> upsrw myups
> 
> I obtain no output.
This is self-consistent: upsrw lists read/write variables, and in your version
of NUT, ups.delay.start (ondelay) and ups.delay.shutdown (offdelay) are not
writable after the driver has started.

To achieve the same effect, you can add "offdelay = 180" to ups.conf,
and restart NUT (only the driver really needs to be restarted, but in Ubuntu
it's one init script for all of NUT).

See the man page for more details on offdelay:
http://www.networkupstools.org/docs/man/blazer_usb.html#_extra_arguments

The new nutdrv_qx driver, which supersedes blazer_usb in 2.7.1 and later, allows
those variables to be changed at runtime.
> My nut version is 2.6.3 (Ubuntu 12.10)
> Drivers are blazer_usb
-- 
Charles Lepple
clepple at gmail