|
On Fri, Oct 21, 2005 at 01:31:55PM -0700, Todd Lyons wrote:
> ankush grover wanted us to know:
>
> >> Always use a standard kernel.
> > FC3 2.6 is also a standard kernel.It has got almost same features which
> >are there in RHEL3.0 may be more.
>
> It's not a standard kernel. RedHat applies tons of patches to modify it
> from a stock 2.6.11 kernel. Take a look at the srpm to see what all
> they are. The gentleman is telling you that to be sure that you are
> seeing problems with your config, make sure there aren't some external
> influences that are creating your problem (ie vendor patches).
>
> Chances are that you simply need to load the appropriate module to
> enable some of the things that you are trying to set. Example:
>
> CentOS41[root@telesto ~]# ls /lib/modules/`uname -r`/kernel/net/ipv4/ipvs/
> ip_vs_dh.ko ip_vs_lblc.ko ip_vs_nq.ko ip_vs_sh.ko
> ip_vs_ftp.ko ip_vs_lblcr.ko ip_vs_rr.ko ip_vs_wlc.ko
> ip_vs.ko ip_vs_lc.ko ip_vs_sed.ko ip_vs_wrr.ko
I believe Fedora Core 3 should have IPVS modules, and the problem
is likely that they are not loaded. There are several ways to fix
this, here are some.
1. Make sure the ipvsadm command is run before sysctl at boot, as
it will automatically load the core ip_vs module.
2. Load the ip_vs module before running sysctl at boot.
On Debian you can ask modules to be loaded at
boot by adding them to /etc/modules
Something _similar_ should exist on Fedora, though
it might be run too late to be useful.
3. Re-run sysctl at the end of boot, after making
sure ip_vs is inserted into the kernel.
--
Horms
|
