Re: When named is not available
First, I've found a solution. The nsswitch.conf file is helpful for my scenario. You can set "hosts: files dns" and the timeouts will never happen. Am Tue, den 06.07.2004 schrieb Bill Moran um 14:42: > It's a standard timeout. The resolver isn't aware of the status of parts > of the network stack below it ... it just waits for 30 seconds for a reply > and then gives up if none comes. It actually sends more queries than just one. That's why it takes that long. > Make sure that /etc/hosts has every possible name for your machine in it, > in addition to "localhost". Any time I've seen one of those WMs get hung > up on DNS, it was becuase it was trying to verify its own host name. I don't expect any traffic when using X-apps locally and while TCP is switched off. Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: When named is not available
Martin <[EMAIL PROTECTED]> wrote: > Hi, > > I have a problem with named in my LAN. My notebook > is sometimes attached to this network and sometimes > not. > > Everything works well when the network cable is plugged-in. > Without the network cable (same network settings), the following > happens: > > - sendmail is waiting for timeout while booting (ok, this is > actually not a big problem, just a little bit annoying) > - host anyhost needs 30 seconds to return with a timeout > - starting any X-application takes 2 minutes 30 seconds till > it appears on the local display > > Remarks about X: > - XFree86 is configured not to accept TCP connections > - the problem above does not occur when running the X-server > without a WM and with twm (affects KDE, Gnome, Xfce) > > Why does the resolver need 30 seconds to look up a host > when named is offline? It's a standard timeout. The resolver isn't aware of the status of parts of the network stack below it ... it just waits for 30 seconds for a reply and then gives up if none comes. This is because it's possible to have different NICs/modems/etc accessing the network, so it would be difficult to teach the resolver when it waited for the the timeout and when not to try. The question I have is: Why are you doing "host somehost" when you're obviously not connected to the network? You're the human in this process, don't give the computer things to do that it obviously can't accomplish and then wonder about it. > Something has changed with XFree, which since recently looking > up hosts (localhost?) when starting an X-application. How do > I turn it off? Make sure that /etc/hosts has every possible name for your machine in it, in addition to "localhost". Any time I've seen one of those WMs get hung up on DNS, it was becuase it was trying to verify its own host name. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
When named is not available
Hi, I have a problem with named in my LAN. My notebook is sometimes attached to this network and sometimes not. Everything works well when the network cable is plugged-in. Without the network cable (same network settings), the following happens: - sendmail is waiting for timeout while booting (ok, this is actually not a big problem, just a little bit annoying) - host anyhost needs 30 seconds to return with a timeout - starting any X-application takes 2 minutes 30 seconds till it appears on the local display Remarks about X: - XFree86 is configured not to accept TCP connections - the problem above does not occur when running the X-server without a WM and with twm (affects KDE, Gnome, Xfce) Why does the resolver need 30 seconds to look up a host when named is offline? Isn't it possible to configure it to react on "no route to host" (for named's IP) correctly? Something has changed with XFree, which since recently looking up hosts (localhost?) when starting an X-application. How do I turn it off? I'm running -CURRENT (2004/07/01). Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"