2008/4/21, Arjen de Korte [EMAIL PROTECTED]:
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
Hi Roger
2008/4/21, Roger Price [EMAIL PROTECTED]:
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
well, that's the biggest problematic of packaging.
none of the solutions are perfect, and both have big pros and cons.
there are still many rooms for improvement there...
Indeed. In the mean time, I have divided the main 'nut' package in the
following sub packages:
- nut (client applications)
On Tue, 22 Apr 2008, Arnaud Quette wrote:
right. the API used is an old one, to have a wide platform support spectrum.
You'll find a 3.0.7 archive here:
http://opensource.mgeops.com/stable/sources/projects/psp/
- Retrieve the .bz2
- extract it, and get into the dir
- call configure a
I loaded g++ which had not been asked for; it requires package
gcc42-c++. The build then went much further, ending in
/usr/lib64/libupsclient.so: undefined reference to `select_read'
/usr/lib64/libupsclient.so: undefined reference to `select_write'
collect2: ld returned 1 exit status
Roger Price wrote:
On Tue, 22 Apr 2008, Arnaud Quette wrote:
right. the API used is an old one, to have a wide platform support spectrum.
You'll find a 3.0.7 archive here:
http://opensource.mgeops.com/stable/sources/projects/psp/
- Retrieve the .bz2
- extract it, and get into the dir
2008/4/21, Arjen de Korte [EMAIL PROTECTED]:
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
2008/4/22, Arjen de Korte [EMAIL PROTECTED]:
well, that's the biggest problematic of packaging.
none of the solutions are perfect, and both have big pros and cons.
there are still many rooms for improvement there...
Indeed. In the mean time, I have divided the main 'nut' package in the
Arnaud Quette wrote:
In the mean time, I have divided the main 'nut' package in the
following sub packages:
- nut (client applications)
- nut-server (drivers and upsd server, requires 'nut')
- nut-snmp (net-snmp based SNMP driver, requires 'nut-server')
- nut-xml (neon based XML
On Tue, Apr 22, 2008 at 11:15:27AM +0200, Arjen de Korte wrote:
Attached is approx 30 sec of output from the following command:
[...]
/* Get HID notifications on Interrupt pipe first */
/* TODO: cap number of times we check for events? */
while ((evtCount =
Is there a chance to use NUT with a Liebert ITON 600 UPS?
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
11 matches
Mail list logo
