Displaying 11 results from an estimated 11 matches for "michaelkintzio".
Did you mean:
michaelkintzios
2014 Apr 05
3
I can't make changes to ups.delay.shutdown to stick
On Apr 5, 2014, at 10:39 AM, Charles Lepple wrote:
> On Apr 5, 2014, at 8:52 AM, Mick <michaelkintzios at 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...
2014 Apr 05
0
I can't make changes to ups.delay.shutdown to stick
On Apr 5, 2014, at 8:52 AM, Mick <michaelkintzios at 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 changed...
2014 Jun 03
0
I can't make changes to ups.delay.shutdown to stick
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 <michaelkintzios at 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...
2014 Jun 04
2
I can't make changes to ups.delay.shutdown to stick
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 <michaelkintzios at 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...
2018 Sep 01
0
upsmon fails to start
...that the config parser stopped parsing at the “#” character. This ends up with a shorter password in upside.users, but a truncated MONITOR line in upsmon.conf. I forget the precedence, but either “\#”, or double quotes around the password should fix it.
> On Sep 1, 2018, at 10:09 AM, Mick <michaelkintzios at gmail.com> wrote:
>
> [upsmon]
> password = 5g>j0vh3NfRW#if
2014 Apr 05
2
I can't make changes to ups.delay.shutdown to stick
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 at localhost
> > Username (suzy): admin
> > Password:
> > OK
>
> This command is sending the value to the UPS (via the usbhid-ups driver).
>
> > $ upsc iDowell at localhost
2014 Jun 04
0
I can't make changes to ups.delay.shutdown to stick
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 <michaelkintzios at 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.
> >>>>
>...
2018 Sep 01
2
upsmon fails to start
Hi All,
I have noticed these messages in my logs:
=========================================
Sep 01 13:14:22 osmc upsd[1450]: listening on 127.0.0.1 port 3493
Sep 01 13:14:22 osmc upsd[1450]: listening on ::1 port 3493
Sep 01 13:14:22 osmc upsd[1450]: listening on 127.0.0.1 port 3493
Sep 01 13:14:22 osmc upsd[1450]: listening on ::1 port 3493
Sep 01 13:14:22 osmc upsd[1450]: Connected to UPS
2018 Sep 01
2
upsmon fails to start
On Saturday, 1 September 2018 17:50:13 BST Charles Lepple wrote:
> I don’t have the code in front of me at the moment, but my guess is that the
> config parser stopped parsing at the “#” character.
I suspected a rogue character was being interpreted and used `backticks`,
'single quotes' and then "double quotes", but all failed. I ended up removing
the offending #
2011 Jan 03
1
Can't get iDowell to work
Hi all, first message to the list. :-)
I've got an iBox made by iDowell:
http://store.apple.com/uk/product/TR423ZM/A
This seems to be similar to the smaller Microdowell UPS:
http://idowell.eu/
I cannot get it recognised by the drivers. This is what I get when I plug in
the USB connector:
Jan 3 19:27:26 compaq kernel: usb 3-2: new low speed USB device using
uhci_hcd and address 47
2014 Apr 05
2
I can't make changes to ups.delay.shutdown to stick
Hi All,
I'm using an iDowell UPS with the usbhid-ups driver:
$ upsc iDowell at localhost
battery.charge: 100
battery.charge.low: 15
battery.runtime: 650
battery.type: Pb acc
device.mfr: iDowell
device.model: iBox
device.serial: 00000001
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto