Displaying 5 results from an estimated 5 matches for "rdagen".
Did you mean:
dragen
2013 Jun 29
2
upsrw doesn't set variable
l?rdagen den 29 juni 2013 11.28.14 skrev Mike.:
8<------------------snip---------------------
Hi Mike,
>
> Thanks for the quick reply.
>
> I checked the log file (which, admittedly, I should have done before I
> posted about the problem :) ).
>
> Here's the command and the c...
2013 Jun 29
0
upsrw doesn't set variable
On 6/29/2013 at 6:16 PM Kjell Claesson wrote:
|l??rdagen den 29 juni 2013 11.28.14 skrev Mike.:
|8<------------------snip---------------------
|Hi Mike,
|>
|> Thanks for the quick reply.
|>
|> I checked the log file (which, admittedly, I should have done before
I
|> posted about the problem :) ).
|>
|> Here's the command...
2013 Jun 29
1
upsrw doesn't set variable
l?rdagen den 29 juni 2013 15.22.44 skrev Mike.:
8<-------------snip-----------------
Sorry for the delay.
> Here is the console output of bcmxcp with -DDD specified:
>
>
> [snip]
> 13.721204 Auto delay on: 2
>
> 13.721243 send_command: (4 bytes) => ab 01 35 1f
&g...
2013 Jun 29
0
upsrw doesn't set variable
On 6/29/2013 at 9:59 AM Charles Lepple wrote:
|On Jun 29, 2013, at 9:45 AM, Mike. wrote:
|
|> On 6/29/2013 at 9:14 AM Mike. wrote:
|>
|> |NUT 2.6.5 on FreeBSD 9.1
|> |
|> |
|> |Why isn't the variable outlet.1.delay.shutdown set with the
following
|> |command?
|> |
|> |
|> |
|> |# upsc PW5125 at localhost | grep "outlet.1.delay.shutdown"
|>
2013 Jun 29
3
upsrw doesn't set variable
On Jun 29, 2013, at 9:45 AM, Mike. wrote:
> On 6/29/2013 at 9:14 AM Mike. wrote:
>
> |NUT 2.6.5 on FreeBSD 9.1
> |
> |
> |Why isn't the variable outlet.1.delay.shutdown set with the following
> |command?
> |
> |
> |
> |# upsc PW5125 at localhost | grep "outlet.1.delay.shutdown"
> |outlet.1.delay.shutdown: -1
> |
> |# upsrw -u au -p ap -s