On Tuesday 16 Mar 2004 11:08 pm, Jim Radford wrote: > On Tuesday 16 Mar 2004 10:28 pm, Alexander Dalloz wrote: > > Am Di, den 16.03.2004 schrieb Jim Radford um 21:53: > > > #Added by me - dunno what it does :) > > > net.ipv4.tcp_ecn = 0 > > > > > > Does that take effect automatically? > > > > No, you need to run "sysctl -p" > > Ahh, cheers for that. Hmmm, since I ran that command I'm seeing this in messages over and over again. Mar 16 20:53:31 mailgate modprobe: modprobe: Can't locate module eth1 Mar 16 20:53:31 mailgate modprobe: modprobe: Can't locate module eth2 Mar 16 20:53:31 mailgate modprobe: modprobe: Can't locate module eth3 Mar 16 20:53:31 mailgate modprobe: modprobe: Can't locate module eth4 Mar 16 20:53:31 mailgate modprobe: modprobe: Can't locate module eth5 Mar 16 20:53:31 mailgate modprobe: modprobe: Can't locate module eth6 Mar 16 20:53:31 mailgate modprobe: modprobe: Can't locate module eth7 Mar 16 20:53:57 mailgate modprobe: modprobe: Can't locate module eth1 Mar 16 20:53:57 mailgate modprobe: modprobe: Can't locate module eth2 Mar 16 20:53:57 mailgate modprobe: modprobe: Can't locate module eth3 Mar 16 20:53:57 mailgate modprobe: modprobe: Can't locate module eth4 Mar 16 20:53:57 mailgate modprobe: modprobe: Can't locate module eth5 Mar 16 20:53:57 mailgate modprobe: modprobe: Can't locate module eth6 Mar 16 20:53:57 mailgate modprobe: modprobe: Can't locate module eth7 What does that mean? -- Jim Radford "If at first you don't succeed - change the DC"
