Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!fu-berlin.de!alaska.zedat.fu-berlin.DE!not-for-mail From: tschach@zedat.fu-berlin.de (Carsten Tschach) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: tcsh and named pauses - more information Date: 18 Sep 1995 23:28:01 GMT Organization: Freie Universitaet Berlin Lines: 67 Message-ID: <43kva1$qrk@fu-berlin.de> References: <43kh0d$84a@fu-berlin.de> NNTP-Posting-Host: alaska.zedat.fu-berlin.de (130.133.1.18) X-Access: 16 17 18 >I've a problem with the named running on my FreeBSD 2.0.5 host. This host >will be connected to the internet soon, but is a local network now. > >In /etc/host.conf the order is 'hosts ... bind', so that he can resolv >local hostnamed directly. As soon as I start the named everything slows down. > >When I start tcsh it needs minutes to finish loading. When I look at the >named-debug I found: > > req: nlookup() id 512 type=1 > req: missed '' as '' (cname=0) > >Why does the tcsh need to call a nlookup? csh didn't this and starts as >fast as normal. > >When you did a rlogin from another host on the LAN it takes hour's >before you will be prompted for the password. In named-debug I found > > req: nlookup(#localhost.infoconcept.de) id 256 type=1 > req: found '#localhost.infoconcept.de' as 'infoconcept.de' (cname=0) > [...] > req: nlookup(#localhost) id 512 type=1 > req: missed '#localhost' as '' (cname=0) > [...] > req: nlookup(#my_very_good_friend.domain) id 768 type=1 > req: missed '#my_very_good_friend.domain' as '' (cname=0) > [...] > req: nlookup(#my_very_good_friend.domain.infoconcept.de) id 1024 type=1 > req: found '#my_very_good_friend.domain.infoconcept.de' as 'infoconcept.de' (cname=0) > >Yes, my local domain is 'infoconcept.de' but the host from which the rlogin >came does appear in /etc/hosts, so there is no nlookup neccessary. > >The dalay time may result from the long timeout conncecting one of the >root nameservers. > >I really don't want to user a nlookup when I login from local hosts, because >every nsrequest will dial out and cost me money. > >I also like to know where or what the "#my_very_good_friend.domain" come >from. So, I found out, that the delays only appear if you logon on one of the virtual consoles. If you login from remote you didn't have to wait. Also a telnet localhost of telnet <hostname> will run tcsh without pausing. It seem that tcsh want to resolve a name for the local console. As soon as a from: appears (in w) everything works fine: 1:27AM up 23:30, 5 users, load averages: 0.00, 0.01, 0.00 USER TTY FROM LOGIN@ IDLE WHAT root v0 - 10:15AM 2:17 -tcsh (tcsh) <--- wait on tcsh tschach p0 eismond-gw 9:01PM - w <--- normal >Thanks for your help, I really need to fix this problem - and understand it. Bye, Carsten Tschach -- -------------------------------+----------------------------------------------- Carsten Tschach | Freie Universitaet Berlin tschach@zedat.fu-berlin.de | Zentraleinrichtung fuer Datenverarbeitung tschach@www.fu-berlin.de | WWW-Admin of http://www.fu-berlin.de/