On 11/2/06, Kjell Claesson [EMAIL PROTECTED] wrote:
Hi Pedro,
Hi
It depends on what dist of Linux you are running. The new type
use udev and hal and the old use coldplug.
So little more info about your system please.
I'm using Ubuntu edgy. That uses udev but since it's a server install
it
On 11/2/06, Pedro Côrte-Real [EMAIL PROTECTED] wrote:
I guess /etc/hotplug/usb/libhidups isn't doing its job correctly on boot.
Oh, and with your udev rules it works fine.
Pedro.
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
On 11/2/06, Kjell Claesson [EMAIL PROTECTED] wrote:
If you restart the upsdrv before you replug the ups, does it find the
ups ?
No it still doesn't.
The thing is that you may start the nut to early. In what runlevel do
you start nut ?
I don't think that's it.
Don't know if ubuntu have
On 11/2/06, Arnaud Quette [EMAIL PROTECTED] wrote:
Hi Pedro,
Hey everyone. Thanks for being so helpful.
are you sure the owner / group doesn't change?
lsusb doesn't show that. I didn't know where to look for the dev files.
I'm running edgy too on the present laptop.
I've not deeply gone
On 11/2/06, Arnaud Quette [EMAIL PROTECTED] wrote:
Oh, and with your udev rules it works fine.
thanks for the feedback Pedro.
I'll have to make a new deb release to address this.
Was it enough to diagnose the problem?
As a side note, the long run approach will be using a new tool called
My new MGE Ellipse Premium 1200 is now working fine. I've tested
pulling the plug and the computer shuts down properly and comes back
up when I replug. The only strange behaviour is that when I put the
power back on the battery shows as being at 86%. If it was at 86% it
should have lasted longer.
On 11/4/06, Charles Lepple [EMAIL PROTECTED] wrote:
Saw your other thread discussing HAL - is your current setup using NUT
to determine when to shut down, or is NUT just telling another
subsystem when the UPS is on battery power (which might just use a
timer, instead of waiting for a low battery
On 11/12/06, Charles Lepple [EMAIL PROTECTED] wrote:
Try setting MAXAGE in upsd.conf to something like 25 or 30.
I tried 120 and it didn't work. Any other suggestions?
Pedro.
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
On 11/12/06, Peter Selinger [EMAIL PROTECTED] wrote:
Try an analogous setting for DEADTIME in upsmon.conf.
This has no effect either.
The connection works like this:
upsmon --- upsd --- driver.
So which timeout you should increase depends on whether the connection
was lost between upsmon
On 11/13/06, Peter Selinger [EMAIL PROTECTED] wrote:
I can only guess. Perhaps you are starting the components in the wrong
order? You have to start:
First the driver (upsdrvctl).
Second upsd.
Third upsmon.
I'm not starting anything by hand. It's the standard ubuntu/debian
init script that
On 11/13/06, Peter Selinger [EMAIL PROTECTED] wrote:
I don't know what their start-stop-daemon command does, but assuming
that it starts upsd as a background process, this could be the source
of the problem. upsd is intended to be started in the foreground; it
will put itself in the background
On 11/14/06, Arjen de Korte [EMAIL PROTECTED] wrote:
Did you also try adding a 5 second sleep between starting upsdrvctl and
upsd? I think the problem lies there, upsd is trying to connect to the
driver that is still in the process of starting up. Since upsd will
periodically retry connecting to
On 11/14/06, Pedro Côrte-Real [EMAIL PROTECTED] wrote:
On 11/14/06, Arjen de Korte [EMAIL PROTECTED] wrote:
Did you also try adding a 5 second sleep between starting upsdrvctl and
upsd? I think the problem lies there, upsd is trying to connect to the
driver that is still in the process
On 11/16/06, Eric Masson [EMAIL PROTECTED] wrote:
When I launch upsd, it barfs vith :
[EMAIL PROTECTED]:~ /usr/local/sbin/upsd -u root
Password:
Network UPS Tools upsd 2.0.4
Connected to UPS [mge]: newhidups-auto
Synchronizing giving up
This looks like the same problem I was having. If
14 matches
Mail list logo
