From owner-freebsd-isp Mon Jan 8 11:14:54 2001 Delivered-To: freebsd-isp@freebsd.org Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (Postfix) with ESMTP id EB2FE37B6B2 for ; Mon, 8 Jan 2001 11:08:28 -0800 (PST) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 14Fgx3-0003G0-00; Mon, 8 Jan 2001 10:23:25 -0800 Date: Mon, 8 Jan 2001 10:23:03 -0800 (PST) From: Tom Samplonius To: Chris Tusa Cc: freebsd-isp@freebsd.org Subject: Re: NFS & NIS interaction issue. In-Reply-To: <3A5A8AA9.42700A6E@oswars.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 8 Jan 2001, Chris Tusa wrote: ... > exports. When I create a new user account via 'adduser' on the > NIS master, I set the home directory to be on an NFS mount located at > '/mnt/nfs/home' when adduser attempts to create the directory, it gives > a CHOWN error. I have determined that it is because the userid does not > exist on the NFS server hosting the home share. The NFS server is ... No, NFS uses numeric IDs in the protocol, so it doesn't matter what users are actually present on the NFS server. You don't need any users on the NFS server if you don't want. The problem is that by default the NFS server mapps the root user to nobody, and only root can chown() files. By default, NFS is setup so that the NFS clients aren't completely trusted, and the "root" user on the client should not necessarily have "root" access to the exported NFS directories. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message