Date: Tue, 12 Jan 1999 11:41:25 +0200 From: Sheldon Hearn <axl@iafrica.com> To: current@FreeBSD.ORG Subject: amd: noconn option exists... Message-ID: <12116.916134085@axl.noc.iafrica.com>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?12116.916134085>