Hello, Does anyone know why diald gets initialised as early as it does under the sysv setup (RedHat 6.0 in my case)? I have a problem with a program (vmware) that needs to grab a local ethernet address (one of the addresses not known to the outside world, 172.etc) for its own purposes, and it does a ping on initialisation to make sure there isn't any other machine on its local net using the chosen address. The idea is apparently that a portable machine might get plugged into an unfamiliar local network. But the result on my machine is that diald, which gets initialised ahead of vmware, dials up to check the address with my ISP's nameserver, which of course doesn't recognise it. If diald weren't initialised until later, the ping would just fail directly, without dialing up, and everything would be fine. I should say that I live in an area where you don't get free local calls, and it just seems wrong to pay British Telecom 5 pence a time for the privilege of booting my machine. There are a couple of obvious things to try. One is to change the order of initialisation, even to move diald into rc.local. That made me wonder why it was at its current position in the first place, and whether I'm likely to trip over something if I do that. Another would be to put in filter rules saying ignore packets to this local ethernet address. In fact, could we ignore packets to any local addresses on principle, or are there cases where people use dial-on-demand to connect to local networks? Any thoughts? Stephen Isard - To unsubscribe from this list: send the line "unsubscribe linux-diald" in the body of a message to [EMAIL PROTECTED]
