|
That is what I was initially thinking of doing, but if someone one the
system
initiates a "service network restart" or /etc/rc.d/init.d/network restart
The settings in the sysctl.conf file would be ignored.
Ray
-----Original Message-----
From: Horms [mailto:horms@xxxxxxxxxxxx]
Sent: Monday, August 12, 2002 9:51 PM
To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: 2.4 Hidden Patch
On Mon, Aug 12, 2002 at 04:13:22PM -0400, Ray Parish wrote:
> I am using the hidden patch on the 2.4 series kernel.
> I have about 1000 ips bound to the lo interface.
> I am having an issue where I set the appropriate proc settings via
> sysctl.conf
> The problem is that the system parses the sysctl.conf file before
> the interfaces exist on the system, so this causes the interfaces to
> come up in "NOT HIDDEN" mode.
> thus I have to run sysctl -p in order to have the proc entries modified.
>
> Is there a way to define lo to always have the default to 1 instead of 0
> in the patch?
I would recommend modifying your boot sequence to run sysctl a second
time. This can be done by either modifying rc.local or adding a new
sysctl init script that gets executed just after the interfaces are
brought up.
--
Horms
_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://www.in-addr.de/mailman/listinfo/lvs-users
|
