On Tue, 19 May 2009, forsite wrote:
> Have anybody tried Cyberpower Value 600E (USB) under FreeBSD?
> usbhid-ups from nut 2.4.1 does not recognize (find) the device on my
> machine.
> [r...@substance /usr/local/libexec/nut]# dmesg | grep uhid
> uhid0: on uhub0
>
> [r...@substance /usr/local/libexe
I am aware of 2 windows nut clients both interestingly called winnut.
One (winnut 2.0.0b) is a service based client based on a port of the but
client code (I think). The other is a GUI client based on (I think
again) on knutclient .
I have corresponded with both authors about a feature reques
For various reasons - I have been trying to get my Desktops and/or
servers to shut-down a fixed time after a power fail - or better still a
fixed time - or a low battery whichever comes first.
I note in my upsc:
*> upsc belkinusb*
battery.charge: 100
battery.charge.low: 30
battery.charge.warnin
On Wed, 20 May 2009, Daniel O'Connor wrote:
> The actual fix is to add an entry in the blacklist for uhid devices
> in /usr/src/sys/dev/usb/usb_quirks.c (around line 115) for the
> vendor/id of your UPS. I think you also need to add an entry
> to /usr/src/sys/dev/usb/usbdevs for the UPS itself. Tha
On 20/05/2009, at 12.11, Richard Chapman wrote:
For various reasons - I have been trying to get my Desktops and/or
servers to shut-down a fixed time after a power fail - or better
still a fixed time - or a low battery whichever comes first.
[cut]
Is there another parameter somewhere -
salut Jean,
2009/5/18 Jean Delvare
> Salut Arnaud,
>
> On Mon, 18 May 2009 16:14:47 +0200, Arnaud Quette wrote:
> > ahah, hem, well to be serious, the game is to identify the report used
> when
> > doing a battery test.
> > so the best would be to only fire usbsnoop when doing that, in order to
I have read the NUT document /usr/share/doc/nut-2.2.0/docs/shutdown.txt
And in particular the section called "RAID Warning".
In response to this section I have added the two lnes, but haven't yet
tested it:
mdadm --readonly /dev/md0
mdadm --readonly /dev/md1
into /etc/rc.d/init.d/halt
Thus:
-
Hi Richard,
> I am aware of 2 windows nut clients both interestingly called winnut.
> One (winnut 2.0.0b) is a service based client based on a port of the but
> client code (I think). The other is a GUI client based on (I think
> again) on knutclient .
>
> I have corresponded with both authors ab
Daniel, fantastic - your patch was exactly what was needed.
> I checked your original post, this should do it.
> I've only tested it compiles though :)
> --- sys/dev/usb/usb_quirks.c (revision 192375)
> +++ sys/dev/usb/usb_quirks.c (working copy)
[r...@substance /usr/local/libexec/nut]# dme
P.S. Apparently, this relates not only to CyberPower, but will likely
be relevant for any UPS-USB device which under GENERIC kernel is
claimed by uhidX (not ugenX) driver.
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alio
On Thu, 21 May 2009, forsite wrote:
> P.S. Apparently, this relates not only to CyberPower, but will likely
> be relevant for any UPS-USB device which under GENERIC kernel is
> claimed by uhidX (not ugenX) driver.
Yes, it is quite annoying..
I wonder if the uhid device could be modified to reject
On Thu, 21 May 2009, forsite wrote:
> Daniel, fantastic - your patch was exactly what was needed.
Great!
> 2_developers: I believe this is a standard situation for CyberPower
> USB devices under FreeBSD. So you may wish to add the solution
> provided by Daniel into the FAQ or at least to mention
12 matches
Mail list logo
