Re: [Nut-upsuser] I can't make changes to ups.delay.shutdown to stick

2014-06-03 Thread Mick
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 wrote: > >

Re: [Nut-upsuser] I can't make changes to ups.delay.shutdown to stick

2014-06-02 Thread Mick
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 wrote: > >>> The upsrw command was designed for changing variables that are > >>> typically stored in non-volatile

Re: [Nut-upsuser] I can't make changes to ups.delay.shutdown to stick

2014-04-06 Thread Mick
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 wrote: > >>> The upsrw command was designed for changing variables that are > >>> typically stored in non-volatile

Re: [Nut-upsuser] I can't make changes to ups.delay.shutdown to stick

2014-04-05 Thread Mick
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 se

[Nut-upsuser] I can't make changes to ups.delay.shutdown to stick

2014-04-05 Thread Mick
1 root nut 11982 Oct 9 06:47 upsmon.conf -rw-r--r-- 1 root root 3891 Sep 22 2013 upssched.conf How is this supposed to work? -- Regards, Mick signature.asc Description: This is a digitally signed message part. ___ Nut-upsuser

Re: [Nut-upsuser] Can't get iDowell to work

2011-01-11 Thread Mick
could not claim interface 0: Device or resource busy 0.266936 Can't retrieve Report 01: Device or resource busy 0.266947 Got disconnected by another driver: Device or resource busy 0.266956 Can't initialize data from HID UPS

Re: [Nut-upsuser] Can't get iDowell to work

2011-01-11 Thread Mick
On 11 January 2011 00:07, Charles Lepple wrote: > On Mon, Jan 10, 2011 at 3:28 PM, Mick wrote: >> On Monday 10 January 2011 12:19:34 you wrote: >>> Hi Mick >>> >>> 2011/1/9 Mick >> >>> > -rwxr-xr-x 1 root root 17840 Jul 25 11:45 /usr/libex

Re: [Nut-upsuser] Can't get iDowell to work

2011-01-11 Thread Mick
On 11 January 2011 07:50, Arjen de Korte wrote: > Citeren Mick : > >> While nut is running, my logs fill up with: > Yes. Make your system not log messages at LOG_DEBUG. Usually you can > configure this in '/etc/syslog.conf'. On a production system, you should not &

Re: [Nut-upsuser] Can't get iDowell to work

2011-01-10 Thread Mick
On 10 January 2011 20:28, Mick wrote: > On Monday 10 January 2011 12:19:34 you wrote: >> Hi Mick >> >> 2011/1/9 Mick > >> > -rwxr-xr-x 1 root root 17840 Jul 25 11:45 /usr/libexec/hald-addon-hid-ups > [snip ...] > >> > Could any of the above be ca

Re: [Nut-upsuser] Can't get iDowell to work

2011-01-10 Thread Mick
On Monday 10 January 2011 12:19:34 you wrote: > Hi Mick > > 2011/1/9 Mick > > -rwxr-xr-x 1 root root 17840 Jul 25 11:45 /usr/libexec/hald-addon-hid-ups [snip ...] > > Could any of the above be causing the clash? > > indeed, /usr/libexec/hald-addon-hid-ups which is

Re: [Nut-upsuser] Can't get iDowell to work

2011-01-09 Thread Mick
/usr/libexec/hald-probe-video4linux -rwxr-xr-x 1 root root 42532 Jul 25 11:45 /usr/libexec/hald-probe-volume -rwxr-xr-x 1 root root 17888 Jul 25 11:45 /usr/libexec/hald-runner Could any of the above be causing the clash? -- Regards, Mick ___ Nut-u

Re: [Nut-upsuser] Can't get iDowell to work

2011-01-04 Thread Mick
On Tuesday 04 January 2011 20:46:26 Arjen de Korte wrote: > Citeren Mick : > > [ snip ] > > >0.171361 refresh_report_buffer: expected 4 bytes, but got 8 > >instead > > > >0.171403 Path: UPS.PowerSummary.DelayBeforeStartup, Type: > >

Re: [Nut-upsuser] Can't get iDowell to work

2011-01-03 Thread Mick
0.073518 - Serial Number: 0001 0.073526 - Bus: 003 0.073534 Trying to match device 0.073543 Device does not match - skipping [snip ...] 0.073737 No appropriate HID device found 0.073749 No matching HID UPS found Same result whether I run it with port auto or port /dev/iDowell. -- Regards, Mick ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Can't get iDowell to work

2011-01-03 Thread Mick
0x0001 Self Powered The device gets picked up by the MSWindows default UPS management facility and from what I was told by the guy who sold it to me it is also read by the default AppleMac power manager (no idea what drivers AppleMacs use for USB connected UPS). -- Regards, Mick __

[Nut-upsuser] Can't get iDowell to work

2011-01-03 Thread Mick
root nut 1778 Jan 1 14:37 upsd.conf -rw-r- 1 root nut 2104 Jan 3 15:47 upsd.users -rw-r- 1 root nut 11988 Jan 3 15:48 upsmon.conf -rw-r--r-- 1 root root 3883 Jan 1 14:02 upssched.conf Is there some other driver, or anything else I could use to get it going? -- Regards, Mick

Re: [Nut-upsuser] Cabac UPS-1700DV2

2009-05-02 Thread mick
On Thu, 23 Apr 2009 13:25:01 mick wrote: > On Fri, 17 Apr 2009 17:51:24 Arjen de Korte wrote: > > Citeren mick : > > > I have a Cabac UPS-1700DV2 > > http://webshop.cabac.com.au/webshop(bD1lbiZjPTUwMA==)/public/catalogue/defa > > >>ult.htm?cat=Z_COMP despite

Re: [Nut-upsuser] Cabac UPS-1700DV2

2009-04-22 Thread mick
On Fri, 17 Apr 2009 17:51:24 Arjen de Korte wrote: > Citeren mick : > > I have a Cabac UPS-1700DV2 > > http://webshop.cabac.com.au/webshop(bD1lbiZjPTUwMA==)/public/catalogue/defa >>ult.htm?cat=Z_COMP despite the unit having only a USB interface it is > > supplied wit

[Nut-upsuser] Cabac UPS-1700DV2

2009-04-16 Thread mick
8 I have had a quick look at NUT but not found an obvious answer and the suggestion that damage is possible discourages me from probing blindly any suggestions, hints, ... would be appreciated mick ___ Nut-upsuser mailing list Nu