From: Trond Myklebust Subject: Re: SM_UNMON again -> kernel Date: 13 Jul 2003 17:25:12 +0200 Sender: nfs-admin@lists.sourceforge.net Message-ID: References: <20030711061615.GA1924@quasar.nro.au.com> <87smpbkt55.fsf@ceramic.fifi.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Lawrence Ong , nfs@lists.sourceforge.net Return-path: Received: from pat.uio.no ([129.240.130.16] ident=7411) by sc8-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 19bij8-0005ka-00 for ; Sun, 13 Jul 2003 08:25:27 -0700 To: Trond Myklebust In-Reply-To: <87smpbkt55.fsf@ceramic.fifi.org> Errors-To: nfs-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Unsubscribe: , List-Archive: >>>>> " " == Philippe Troin writes: > Trond Myklebust writes: >> Is /etc/hosts consistent? The kernel only sends MON/UNMON >> requests on the loopback port, so this suggests that something >> is translating 127.0.0.1<->"mymachine" instead of to >> "localhost". > I've also been seeing this forever... Which also means that > locks are never recovered after a server reboot, which is midly > annoying. The *same* error, with a message that appears not to be originating from 127.0.0.l? > What do you mean by "consistent" /etc/hosts? I mean crap like 127.0.0.l localhost mymachine in /etc/hosts, together with a DNS entry translates the name "mymachine" into another IP address. Believe me. It's been done... Cheers, Trond ------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs