Luca Ferrari wrote: > I've noted on different system that when an ip route changes, the kernel keeps > the old one in a cache (I suppose) for a while. For example, if in > you /etc/hosts you have an entry: > 192.168.1.201 fluca fluca > and ping fluca it will try to connect to 192.168.1.201. > Now if you change the address and immediatly reping it, it will try again the > old host for a while. After a minute the system should be able to use the new > address. This also applies to routes. > Is there a way to force a cache-clear, thus modifications are immediatly > visible? 1. What does this have to do with routing? Unless I'm misunderstanding the above, this is a name-service issue. 2. Are you using nscd? If so, try "/etc/rc.d/init.d/nscd restart". -- Glynn Clements <glynn.clements@xxxxxxxxxx> - : send the line "unsubscribe linux-admin" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
