Comment 20 for bug 779512

2011/7/13 Martin Ewing <email address hidden>

> Arnaud,
>
> Thanks for the reply! I imagine you are correct. I ran the command you
> suggested (below). Apparently nut knows the device it should connect to,
> but that device is "busy". And running as root doesn't overcome the
> problem... (And I don't know why I should have to make /var/run/nut,
> either.)
>

this specific issue with claim is generally bound to another instance of the
driver still running.

> I am not well versed in Ubuntu bug reporting. Do you think I need to
> submit
> this separately? Or should I just wait until the next release? (The lazy
> way out.)
>

for now, we'll focus on hunting your issue here.
if it goes beyond another 2 mails, then we'll check for creating a dedicated
bug report, to be able to close it through 2.6.1 upload, while not forgiving
you ;)

cheers,
Arnaud
--
Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/