On Thu, Feb 07, 2008 at 08:24:13AM +0100, Arjen de Korte wrote:
> > The previous driver would stop by typing a CTRL-C when
> > running interactively in debug mode. The new driver will not
> > respond to a CTRL-C. It does not respond to a "kill -1",
> > "kill -2" or a "kill -15" either (Which may or
> The previous driver would stop by typing a CTRL-C when
> running interactively in debug mode. The new driver will not
> respond to a CTRL-C. It does not respond to a "kill -1",
> "kill -2" or a "kill -15" either (Which may or may not be
> OK).
It *will* respond to CTRL-C, but due to the increase
On Feb 6, 2008 9:55 PM, John Darrah <[EMAIL PROTECTED]> wrote:
> On Wed, Feb 06, 2008 at 09:29:47AM +0100, Arjen de Korte wrote:
> > > After updating from 2.2.0 to 2.2.1, the following command
> > > seems to go into loop and becomes unresponsive except for a
> > > "kill -9":
> > >
> > > /lib/nut/us
On Wed, Feb 06, 2008 at 09:29:47AM +0100, Arjen de Korte wrote:
> > After updating from 2.2.0 to 2.2.1, the following command
> > seems to go into loop and becomes unresponsive except for a
> > "kill -9":
> >
> > /lib/nut/usbhid-ups -u root -DDD -a trippy
>
> Running the driver in debug mode has a
> After updating from 2.2.0 to 2.2.1, the following command
> seems to go into loop and becomes unresponsive except for a
> "kill -9":
>
> /lib/nut/usbhid-ups -u root -DDD -a trippy
Running the driver in debug mode has always prevented it from
backgrounding, so nut-2.2.0 would also require a 'kill
OS: Linux (Linux ares 2.6.22-3-686 #1 SMP)
Dist: Debian (testing)
UPS: Tripp Lite Omni1000 LCD
After updating from 2.2.0 to 2.2.1, the following command
seems to go into loop and becomes unresponsive except for a
"kill -9":
/lib/nut/usbhid-ups -u root -DDD -a trippy
It seem that the previous v
6 matches
Mail list logo
