From owner-freebsd-current@FreeBSD.ORG Thu Oct 30 03:27:00 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 740BB16A4CE for ; Thu, 30 Oct 2003 03:27:00 -0800 (PST) Received: from firecrest.mail.pas.earthlink.net (firecrest.mail.pas.earthlink.net [207.217.121.247]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF72043FB1 for ; Thu, 30 Oct 2003 03:26:59 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from user-2ivfim6.dialup.mindspring.com ([165.247.202.198] helo=mindspring.com) by firecrest.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 1AFAx3-00078u-00; Thu, 30 Oct 2003 03:26:54 -0800 Message-ID: <3FA0F54D.1119C8B8@mindspring.com> Date: Thu, 30 Oct 2003 03:26:05 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Andy Hilker References: <20031029095404.E28526@doriath.saers.com> <20031029174012.GA92073@goodhope.crypta.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4802c02d67900a489bee1e85df06a849093caf27dac41a8fd350badd9bab72f9c350badd9bab72f9c cc: freebsd-current@freebsd.org Subject: Re: Postfix locks 5.1-servers? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2003 11:27:00 -0000 Andy Hilker wrote: > i am using current. Similar problems *without* postfix. Login via ssh > results in print motd, but nothing more. > Login on local console results in nothing after pressing enter on > username. I think you have a different problem than the one that started this thread. It's very common, for shell prompts which include the host name, or for some shells that are too stupid to realize that the prompt string does not require the host name, to do a DNS query in order to get the name of the machine they are running on. The normal result for this when the DNS server is unavailable (or is accidently firewalled) is to lock up, either temporarily, or permananently, depending on how badly the shell wants the information. If the session is already established, and you aren't using "bash" as your shell, then typing "^C" might get you a default prompt and drop you to a shell. Note that a number of these shells are incredibly stupid, and will attempt to get the host name (and canonize it) on each prompt display. It's often useful to install the real "sh" (ash) or the real csh (not zsh, not tcsh, not bash, etc.) from ports, so that the stupid shell doesn't cause this sort of problem. Alternately, you can run a split horizon DNS and/or a local caching DNS server with a preloaded cache for all local machines to avoid a real DNS lookup. -- Terry