|
On Wed, 21 Mar 2001, Joseph Mack wrote:
> Kyrian wrote:
> >
> > > > C'est ainsi que Kyrian (kyrian@xxxxxxx) s'exprimait:
> > > >
> > > > ] static rwlock_t __ip_vs_svc_lock = RW_LOCK_UNLOCKED;
> > > > ]
> > > > I just removed the static word in that definition so that the other
> > > > module may use it. BTW the generated kernel produced (ipvs included in
> > > > the
> > > > kernel not as modules) has a Null pointer dereference :-(
> > > It compiled for me. This is a surprise, it worked and it's not supposed
> > > to :-)
> >
> > Hi,
> >
> > I'm still having troubles.
> >
> > I assume that you don't make all of the LVS stuff as modules, and that
> > some of it has to actually be built in to the kernel proper? Otherwise
> > what I've done would work...? ;*|
>
> you can compile it into the kernel or do as modules. I've only
> done the module method.
>
> You have to patch the kernel symbol table (see the README in the
> ipvs directory). You then compile the kernel with your favorite
> options. (.config attached)
>
> Reboot into the new kernel.
>
> The compile the ipvs modules with the makefile in /ipvs-x.x.x/ipvs.
> I then tar-untar all the *.o files into
> /lib/modules/`uname -r`/kernel/net/ipvs
>
> Then run depmod -a. It will complain of unresolved symbols in two
> of the ip_vs*.o files. They aren't supposed to be in /lib/modules
> and are only there because it was easier to copy everything rather
> than just the files needed. You can ignore this error - nothing will
> ever try to load those files as modules.
>
> Then do insmod ip_vs
>
> I don't know if this is the way that Wensong planned, but it works.
>
Will add the feature soon, i.e. "modprobe ip_vs" when the ipvs service
isn't available.
Thanks,
Wensong
> don't forget to make and install the new ipvsadm
>
> Joe
>
>
|
