Roger Price wrote:
The better strategy would be to start a upssched timer (I'll call this
'powerout') as soon as the power is lost. If the power returns, cancel the
timer and it is business as usual. When the 'powerout' timer elapses after
two minutes, you start a second timer (I'll call this
John Darrah wrote:
I have determined that the the socket is never created because the program
never reaches dstate_init().
It *must* reach this, otherwise it would never reach the part where it
continuously loops through upsdrv_updateinfo().
[...]
The following is a section of
2008/4/20, Arjen de Korte [EMAIL PROTECTED]:
I'll try them tomorrow; meanwhile, another n00bie question : What does
nut-hal do? Do I need it?
The nut-hal package is a package that contains the hal drivers and fdi
file udev rules.
As you are using a usb ups, you may use this
2008/4/21, Arjen de Korte [EMAIL PROTECTED]:
Arnaud Quette wrote:
I previously splitted the Debian packages in nut, nut-usb, nut-cgi,
nut-snmp, nut-dev, nut-doc (empty ATM) and now nut-hal-drivers. I've
then re-integrated the USB part into the core package since it's usual
to have
Arnaud Quette wrote:
I previously splitted the Debian packages in nut, nut-usb, nut-cgi,
nut-snmp, nut-dev, nut-doc (empty ATM) and now nut-hal-drivers. I've
then re-integrated the USB part into the core package since it's usual
to have libusb, even on headless server (and USB tend to become
Arnaud Quette wrote:
No, and that's because I doubt that openSUSE will follow this approach.
Historically, there hasn't been too much interest in splitting packages,
since SuSE (now openSUSE) attempts to create a working configuration out of
the box. Therefor, it made little sense to split
On Sun, 20 Apr 2008, Roger Price wrote:
# /etc/ups/upssched.conf
CMDSCRIPT /usr/sbin/upssched-cmd
PIPEFN /var/run/ups/upssched.pipe
LOCKFN /var/run/ups/upssched.lock ...
No surprise here, it's just more n00b fumbling. The correct answer, which
is provided by the rpm but which I wrongly
Roger Price wrote:
No surprise here, it's just more n00b fumbling. The correct answer, which
is provided by the rpm but which I wrongly ignored, is:
# /etc/ups/upssched.conf
CMDSCRIPT /usr/sbin/upssched-cmd
PIPEFN /var/lib/ups/upssched/upssched.pipe
LOCKFN
2008/4/20, Arjen de Korte [EMAIL PROTECTED]:
Roger Price wrote:
...
As you are using a usb ups, you may use this instead of the nut package.
If you install it, the ups gets hotplugged by udev hal and would show up
as a
battery in the power monitor in Gnome. (should be the same in
Arnaud Quette wrote:
There is no /var/state in openSUSE 10.3, so I changed PIPEFN and LOCKFN to
/var/run and defined directory /var/run/ups.
We need a pre3 to fix this since this has been a long standing bug. This
path is hardcoded in the example configuration, where running
On Mon, 21 Apr 2008, Arnaud Quette wrote:
Also note that the PSP 3.0.4 is the one provided by MGE *UPS Systems*.
I don't think this one is maintained anymore, so you really want to
switch to the MGE *Office Protection Systems which is the 3.0.6 one,
available here:
On Mon, 21 Apr 2008, Roger Price wrote:
On Mon, 21 Apr 2008, Arnaud Quette wrote:
A source RPM for SuSE is also available, but I'm not sure it's x64 ready!
http://opensource.mgeops.com/stable/sources/suse/
I had confused mgeups and mgeops. I downloaded the source rpm and ran the
On Mon, Apr 21, 2008 at 09:36:07AM +0200, Arjen de Korte wrote:
John Darrah wrote:
I have determined that the the socket is never created because the program
never reaches dstate_init().
It *must* reach this, otherwise it would never reach the part where it
continuously loops through
13 matches
Mail list logo
