Alex Malinovich said: > I just checked it and that was it as it turns out. Interestingly enough, > the problem was not that the search line was missing, but that it had > \000 appended to the end of it. Since his was the first computer that I
sounds like you may have a win32 DHCP server? or perhaps if you have some sort of broadband you get an IP from a remote DHCP server which may be runing win32. I have seen similar behavior(it may be exactly the same I don't remember, been about 2 years since I've been in a Win32 DHCP server enviornment) where a win32 DHCP server did this. the dhcp client should have a way to determine what IP gave you the DHCP IP, at which point there are several tools available to attempt to identify the OS of the machine on that IP. at the time my workaround was to hack up the DHCP scripts so it would not modify resolv.conf when it recieved DHCP info. This was back in the early days of 2.2 and 2.1, I'm sure DHCP config has changed a lot since..so I am not completely sure where to start, but a good place would be perhaps to grep the entire /etc tree for resolv.conf and see what scripts have references to it nate -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
