On Jun 3, 2014, at 1:28 AM, Mick wrote:
On Saturday 05 Apr 2014 16:28:24 Charles Lepple wrote:
On Apr 5, 2014, at 10:39 AM, Charles Lepple wrote:
On Apr 5, 2014, at 8:52 AM, Mick michaelkintz...@gmail.com wrote:
The upsrw command was designed for changing variables that are
typically stored
On Wednesday 04 Jun 2014 03:07:27 Charles Lepple wrote:
On Jun 3, 2014, at 1:28 AM, Mick wrote:
On Saturday 05 Apr 2014 16:28:24 Charles Lepple wrote:
On Apr 5, 2014, at 10:39 AM, Charles Lepple wrote:
On Apr 5, 2014, at 8:52 AM, Mick michaelkintz...@gmail.com wrote:
The upsrw command was
On Saturday 05 Apr 2014 16:28:24 Charles Lepple wrote:
On Apr 5, 2014, at 10:39 AM, Charles Lepple wrote:
On Apr 5, 2014, at 8:52 AM, Mick michaelkintz...@gmail.com wrote:
The upsrw command was designed for changing variables that are
typically stored in non-volatile memory on the UPS.
On Apr 5, 2014, at 7:18 AM, Mick wrote:
$ upsrw -s ups.delay.shutdown=30 iDowell@localhost
Username (suzy): admin
Password:
OK
This command is sending the value to the UPS (via the usbhid-ups driver).
$ upsc iDowell@localhost ups.delay.shutdown
30
And this command ends up reading the
Thanks Charles,
On Saturday 05 Apr 2014 12:53:06 Charles Lepple wrote:
On Apr 5, 2014, at 7:18 AM, Mick wrote:
$ upsrw -s ups.delay.shutdown=30 iDowell@localhost
Username (suzy): admin
Password:
OK
This command is sending the value to the UPS (via the usbhid-ups driver).
$ upsc
On Apr 5, 2014, at 8:52 AM, Mick michaelkintz...@gmail.com wrote:
The upsrw command was designed for changing variables that are typically
stored in non-volatile memory on the UPS. Unfortunately, your UPS doesn't
seem to do that.
Well, if it doesn't do that, how come upsc reports the
On Apr 5, 2014, at 10:39 AM, Charles Lepple wrote:
On Apr 5, 2014, at 8:52 AM, Mick michaelkintz...@gmail.com wrote:
The upsrw command was designed for changing variables that are typically
stored in non-volatile memory on the UPS. Unfortunately, your UPS doesn't
seem to do that.
Well,
7 matches
Mail list logo
