guys,
2010/3/9 Chuck Short:
> Unfortunately it hasnt been tested by me. I rather get Arnaud's thoughts
> on this.
I've not been able to do much testing on DK-p and none UPower.
what I can say for the DK-p side (which theoretically should be
applicable to UPower) is:
- if a USB UPS is plugged, DK-p will take the hand on it.
- if NUT is then started, it will kick off DK-p (by detaching the
hiddev kernel driver, and so cutting the link used by DK-p), and will
take the hand on the device.
- if NUT is then stopped, you will have to unplug / replug your UPS'
USB cord to generate a new udev event so that DK-p probes the new
devices and restore the link to it.
So, I'm confident that this upload won't break DK-p or UPower, and
will fixe many things.
as a side note, I have a 2.4.3-2 underway which solves the bull**it
introduced by Scott James for refreshing the USB bus on postinst...
The result is that any USB user has to unplug / plug back his UPS' USB
cord to get udev apply the right rules.
ie, in nut.postint:
udevadm trigger --action=change
should be replaced by
udevadm trigger --subsystem-match=usb
though I've not finished investigation / work on this, and won't
commit on an upload date.
this is limited to new installation where the UPS is already plugged in.
I hope this helps...
Arnaud
--
Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
--
FFE for nut 2.4.3
https://bugs.launchpad.net/bugs/535152
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
