From owner-freebsd-current Thu Apr 12 7: 1:14 2001 Delivered-To: freebsd-current@freebsd.org Received: from infres.enst.fr (infres-192.enst.fr [137.194.192.1]) by hub.freebsd.org (Postfix) with ESMTP id 01D7337B423 for ; Thu, 12 Apr 2001 07:01:12 -0700 (PDT) (envelope-from quinot@inf.enst.fr) Received: from shalmaneser.enst.fr (shalmaneser.enst.fr [137.194.160.128]) by infres.enst.fr (Postfix) with ESMTP id 41CE345451 for ; Thu, 12 Apr 2001 16:01:10 +0200 (MET DST) Received: by shalmaneser.enst.fr (Postfix, from userid 11117) id 7A529112DF; Thu, 12 Apr 2001 16:01:06 +0200 (CEST) Date: Thu, 12 Apr 2001 16:01:06 +0200 From: Thomas Quinot To: freebsd-current@freebsd.org Subject: NFS export to netgroup with duplicate hosts Message-ID: <20010412160106.A10472@shalmaneser.enst.fr> Reply-To: Thomas Quinot Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi -CURRENT users, I wonder what should happen when a volume is exported through NFS to a netgroup that contains duplicate hosts. At this site, we have a number of netgroups which contain both qualified and unqualified host names, as in MyNetgroup (somehost,-,-) (somehost.dom.ain,-,-) ... and I have the following line in /etc/exports: /usr -alldirs MyNetgroup (/usr is a ffs file system mount point). When mountd attempts to register the export list with the kernel, the first attempt to export to somehost succeeds, and then the second fails with EPERM ("can't change attributes for /usr"), and I am left with an empty kernel export list. This used to work with 5.0-CURRENT as of a few months ago. Shouldn't such an export work as expected? Thomas. -- Thomas Quinot ** Département Informatique & Réseaux ** quinot@inf.enst.fr ENST // 46 rue Barrault // 75634 PARIS CEDEX 13 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message