Thank you for your troubles and research. Unfortunately both links have
nothing to do with my current problem ;).
see Bug #270774:
The last statement is important and the Debian folks should do that
ASAP. I've done the same thing in our company distribution. We have a
ipvsadm-2.2, a ipvsadm-2.4 and a ipvsadm-2.6. Whichever kernel you boot,
you get the right tool with it.
My problem is:
I've got a Debian testing based Linux system on a sparc64 box. I try to
get LVS running on a vanilla 2.4.27 kernel. The kernel module loads and
runs absolutely fine.
As stated, I've also downloaded the ipvsadm-1.21 source which should be
correct for the latest 2.4.x IPVS version. Compiling it, with the
/usr/src/linux includes (which is correct regarding my self-made kernel)
gives me a binary which does not work as outlined in my first email.
Any hints as to why this is so? I'll stick my nose into the code now for
real ... sigh, my girlfriend will kill me. I suspect some 64bit
uncleanliness or something along those lines. For more information:
gforge@sf-netra:~$ gcc -v
Reading specs from /usr/lib/gcc-lib/sparc-linux/3.3.4/specs
Configured with: ../src/configure -v
--with-system-zlib --enable-nls --without-included-gettext
--enable-__cxa_atexit --enable-clocale=gnu --enable-debug
--enable-java-gc=boehm --enable-java-awt=xlib --with-cpu=v7
Thread model: posix
gcc version 3.3.4 (Debian 1:3.3.4-13)
gforge@sf-netra:~$ uname -a
Linux sf-netra 2.4.27 #1 Sat Oct 16 17:14:21 CEST 2004 sparc64 GNU/Linux
Maybe the Debian folks have already fixed some of those in their
patches, will have a look at those first.
Roberto Nibali, ratz
ps: I see that we've got a commercial touch now with the new site :)
'[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq' | dc