Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!uwm.edu!news.alpha.net!news.mathworks.com!udel!gatech!swrinde!hookup!caen!hearst.acc.Virginia.EDU!murdoch!paco From: paco@Virginia.EDU (Brian -Paco- Hope) Subject: resolve.conf vs. resolv.conf Message-ID: <D05wwL.1A5@murdoch.acc.Virginia.EDU> Sender: paco@quokka.acc.Virginia.EDU (Brian -Paco- Hope) Organization: Some Loco Hombre Date: Fri, 2 Dec 1994 02:43:33 GMT Lines: 23 I think this is just an oversight in the initial setup. Perhaps it was done conciously for a reason that I can't think of. I was trying to get domain name service running (i.e. I knew a name server that I wanted to get my names from). I added the appropriate IP numbers and names in my /etc/resolve.conf file, but nothing changed. I couldn't figure out what wasn't working. Finally it dawned on me that on all other systems I've worked on, this file is named /etc/resolv.conf (only one 'e' in resolv) When I renamed the file, the daemon picked up on it and my names were resolved without a problem. I didn't even have to send a signal to the daemon. Seems to me that this would cause inexperienced users a bit of a headache. Not that I'm a guru, but I don't know that many people would think of renaming the file as a likely solution. Maybe I'm wrong. Anyways, I just wanted to share this with the rest of you hoping to save some other unsuspecting user a little bit of time. Paco -- |Brian "Paco" Hope (Team OS/2) | (804) 982-2294, fax:(804) 982-2214 | |Department of Computer Science | email: paco@virginia.edu | |University of Virginia | http://uvacs.cs.virginia.edu/~bah6f/ |