On Sat, 17 Nov 2007 22:24:01 +0100
Arjen de Korte <[EMAIL PROTECTED]> wrote:
> You trimmed off the initial (and most interesting) part of the startup
> of this driver. Don't do that, unless we ask you to do so.
>
> Best regards, Arjen
Okay..
Here is the output. I saved it to a file for bet
hanji wrote:
> Strange. Looks like my init script already does this:
>
> start() {
> ebegin "Starting upsd"
> # clean up first
> pkill -u root -x upsd
> sleep 1s
> rm -f ${pidfile}
> # now start up
> start-stop-daemon --start --quiet --exec
On Sat, 17 Nov 2007 21:24:27 +0100
Arjen de Korte <[EMAIL PROTECTED]> wrote:
> hanji wrote:
>
> > Thanks for replying to my email. I updated to 2.2.0, and I'm running
> > into the same problem, but also encountered other issues. After
> > upgrading to 2.2.0 and using the usbhid-ups driver, I was
hanji wrote:
> Thanks for replying to my email. I updated to 2.2.0, and I'm running
> into the same problem, but also encountered other issues. After
> upgrading to 2.2.0 and using the usbhid-ups driver, I was not able to
> get a clean restart of upsd.
>
> /etc/init.d/upsd restart
> * Stopping u
On Sat, 17 Nov 2007 16:28:10 +0100 (CET)
"Arjen de Korte" <[EMAIL PROTECTED]> wrote:
> First, upgrade to at least nut-2.2.0. If that doesn't fix this, come back
> here for instructions on how to run the driver in debug mode, so that we
> can figure out what is going on.
>
> Best regards, Arjen
>
> I just discoverd NUT and I'm lovin' it. I was very successful getting
> nut to monitor a CyberPower UPS along with having a Linux slave for a
> friend of mine. I've come to a snag on my personal system though. I
> currently have two Back-UPS XS 1200 APC UPSs, and I'm seeing
> notifications of lo
6 matches
Mail list logo
