From owner-freebsd-current Tue Jan 12 01:42:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23781 for freebsd-current-outgoing; Tue, 12 Jan 1999 01:42:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA23775 for ; Tue, 12 Jan 1999 01:42:10 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1) id 1000KD-00039R-00 for current@freebsd.org; Tue, 12 Jan 1999 11:41:25 +0200 From: Sheldon Hearn To: current@FreeBSD.ORG Subject: amd: noconn option exists... Date: Tue, 12 Jan 1999 11:41:25 +0200 Message-ID: <12116.916134085@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, I'm using ELF 3.0-CURRENT as of Friday last week. I've just noticed the following in /etc/messages: amd[11641]: noconn option exists, and was turned OFF! (May cause NFS hangs on some systems...) src/contrib/amd/libamu/mount_fs.c has this to say (indentation removed): /* * Some OSs want you to set noconn always. Some want you to always turn * it off. Others want you to turn it on/off only if NFS V.3 is used. * And all of that changes from revision to another. This is * particularly true of OpenBSD, NetBSD, and FreeBSD. So, rather than * attempt to auto-detect this, I'm forced to "fix" it in the individual * conf/nfs_prot/nfs_prot_*.h files. */ Are these messages harmless warnings that can be turned off, or does this indicate that I falsely estimated the success of my transition to CURRENT? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message