A.Lizard wrote:
>
> As I said earlier, I got it working using the -u root option.
>
> I'm running on the Debian distribution.
>
> Upon upsmon -c fsd , it shuts down the workstation, but NOT the UPS. In
> order to shut down both, I first tried Peter Selinger's shutdown patch for
> init.d halt
As I said earlier, I got it working using the -u root option.
I'm running on the Debian distribution.
Upon upsmon -c fsd , it shuts down the workstation, but NOT the UPS. In
order to shut down both, I first tried Peter Selinger's shutdown patch for
init.d halt :
note: program location
That is great news! -- Peter
A.Lizard wrote:
>
> At 12:41 PM 2/27/07, you wrote:
> It now works - with minor issues.
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
At 12:41 PM 2/27/07, you wrote:
It now works - with minor issues.
Hi again,
several people have already responded to this message, so I will be
brief. I just wanted to reiterate that the output below is exactly as
it should be. I don't see any bugs there.
The problem rather seems to be that you
Peter Selinger wrote:
Basically, you need to pass the same system user to "-u" on both the
driver and upsd.
>>> How?
>> See 'man 3 upsd'.
> Or perhaps 'man 8 upsd'.
I really need to go to bed... :-)
Best regards, Arjen
___
Nut-upsuser mailin
Arjen de Korte wrote:
>
> A.Lizard wrote:
>
> >> Basically, you need to pass the same system user to "-u" on both the
> >> driver and upsd.
> >
> > How?
>
> See 'man 3 upsd'.
Or perhaps 'man 8 upsd'.
-- Peter
___
Nut-upsuser mailing list
Nut-upsuse
A.Lizard wrote:
>> Basically, you need to pass the same system user to "-u" on both the
>> driver and upsd.
>
> How?
See 'man 3 upsd'.
Best regards, Arjen
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org
A.Lizard wrote:
> >> >This is also expected, since it sounds like you still have the driver
> >> >running with "-u root".
> >>
> >>I haven't been able to get it to run any other way - newhidups outputs
> >>(non-root and root) below.
> >
> >Right. The fact that it works when both the driver and upsd
Hi again,
several people have already responded to this message, so I will be
brief. I just wanted to reiterate that the output below is exactly as
it should be. I don't see any bugs there.
The problem rather seems to be that you are not following the
instructions precisely. What is the point of
At 05:31 AM 2/27/07, you wrote:
[for general debugging like this, please keep the list copied.]
On 2/27/07, A.Lizard <[EMAIL PROTECTED]> wrote:
At 05:09 AM 2/27/07, you wrote:
>On 2/27/07, A.Lizard <[EMAIL PROTECTED]> wrote:
>>At 04:48 AM 2/27/07, you wrote:
>> >On 2/27/07, A.Lizard <[EMAIL PRO
[for general debugging like this, please keep the list copied.]
On 2/27/07, A.Lizard <[EMAIL PROTECTED]> wrote:
At 05:09 AM 2/27/07, you wrote:
>On 2/27/07, A.Lizard <[EMAIL PROTECTED]> wrote:
>>At 04:48 AM 2/27/07, you wrote:
>> >On 2/27/07, A.Lizard <[EMAIL PROTECTED]> wrote:
>> >>and "upsd ge
On 2/27/07, A.Lizard <[EMAIL PROTECTED]> wrote:
At 04:48 AM 2/27/07, you wrote:
>On 2/27/07, A.Lizard <[EMAIL PROTECTED]> wrote:
>>and "upsd gets a 'connection refused' message" was a typo, I meant *upsc* .
>>I haven't tried running upsd since building the wrong source package.
>
>upsc connects t
> The latest version available packaged for Debian that I can find on the
> Debian site is 2.0.5-3, the one I've previously had trouble with.
The problems you have don't seem to be related to the anything wrong with
the code, but rather with the configuration. So I'd go with the packaged
version
On 2/27/07, A.Lizard <[EMAIL PROTECTED]> wrote:
and "upsd gets a 'connection refused' message" was a typo, I meant *upsc* .
I haven't tried running upsd since building the wrong source package.
upsc connects to upsd (this is the network portion of "Network UPS
Tools"), so upsd needs to be runni
At 03:20 AM 2/27/07, you wrote:
Thanks. What I wanted was the latest version short of building it from the
code in subversion. (which I consider kind of a last resort, since I've
The latest version available packaged for Debian that I can find on the
Debian site is 2.0.5-3, the one I've previo
> I tried building nut 2.0.5 pre2 from source using the user=nut and make
> usb options, and got the same results.
That's an old version, please don't use that anymore. The latest stable
version is nut-2.0.5. Furthermore, you should specify the same '-u user'
for both upsdrvctl and upsd.
> It wo
I tried building nut 2.0.5 pre2 from source using the user=nut and make usb
options, and got the same results. It works from -u root, but upsd gets a
"connection refused" message.
Same messages when I run newhidups directly. I can't find any processes
connected to the UPS.
I am open to sugge
At 06:14 PM 2/23/07, you wrote:
Back to square one. Is there any other process running that might
already be attached to that device? -- Peter
these are the only hal processes running
terrarium:/usr/lib/hal# ps axjf
/usr/sbin/hald
2590 2591 2590 2590 ? -1 S0 0:00 \_ ha
Back to square one. Is there any other process running that might
already be attached to that device? -- Peter
A.Lizard wrote:
>
> At 01:01 PM 2/23/07, you wrote:
> I tried the procedure - no change.
>
> terrarium:/usr/lib/hal# /lib/nut/newhidups -DDD -a belkin-ups
> Network UPS Tools: 0.28 US
At 01:01 PM 2/23/07, you wrote:
I tried the procedure - no change.
terrarium:/usr/lib/hal# /lib/nut/newhidups -DDD -a belkin-ups
Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5)
debug level is '3'
Checking device (050D/0551) (002/006)
- VendorID: 050d
- ProductID: 0551
At 01:01 PM 2/23/07, you wrote:
[please, keep the traffic on the list]
Now that I'm awake, no problem.
This is how message traffic is showing up from the list:
Date: Fri, 23 Feb 2007 21:27:57 +0100
From: "Arnaud Quette" <[EMAIL PROTECTED]>
To: "Peter Selinger" <[EMAIL PROTECTED]>
Subject: Re:
[please, keep the traffic on the list]
2007/2/23, A.Lizard <[EMAIL PROTECTED]>:
At 05:12 AM 2/23/07, you wrote:
>Not sure you've seen it, so I step up:
>
>in the "ps" output, there is: hald-addon-hid-ups
>this is an HAL addon, based upon the same code as our old hidups...
>this is what I'm worki
Not sure you've seen it, so I step up:
in the "ps" output, there is: hald-addon-hid-ups
this is an HAL addon, based upon the same code as our old hidups...
this is what I'm working on in NUT to replace.
I've not thought at it before since I've completely disabled hiddev
support in kernel for MGE
This is perhaps a permissions problem.
You need to give newhidups the "-u root" option, or else it will drop
root privileges and probably not be able to open the device. Also,
the newhidups driver has no "start" argument.
Try this: kill all running drivers, and stop upsd and upsmon. Then:
/lib
suAt 09:08 AM 2/21/07, you wrote:
looks like you were right, but even with the process killed the problem
doesn't go away. Chalk up the typos in the following to my starting this
before finishing my first cup of coffee.
thanks
A.Lizard
[EMAIL PROTECTED]:~$ ps -ef | grep ups
root 2659
This looks like another driver is already attached to your Belkin.
Perhaps you already have a copy of newhidups running in the
background, or perhaps as a zombie process left over from previous
experiments. Try
ps -ef | grep ups
to see what is running, and kill it if necessary. -- Peter
A.Lizard
26 matches
Mail list logo
