Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 Oct 2001 16:02:46 -0400 (EDT)
From:      Robert Watson <rwatson@FreeBSD.org>
To:        Dag-Erling Smorgrav <des@ofug.org>
Cc:        Alfred Perlstein <alfred@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   Re: cvs commit: src/etc/defaults rc.conf
Message-ID:  <Pine.NEB.3.96L.1011019154254.72418C-100000@fledge.watson.org>
In-Reply-To: <xzpd73kab3g.fsf@flood.ping.uio.no>

next in thread | previous in thread | raw e-mail | index | archive | help

On 18 Oct 2001, Dag-Erling Smorgrav wrote:

> Alfred Perlstein <alfred@FreeBSD.org> writes:
> >   Log:
> >   Update to note that rpc.statd and rpc.lockd are now needed for
> >   client side NFS mounts.
> 
> How about "documenting" this dependency in rc.network, as was done for
> the portmapper? 

Running the current nfs_lock.c code can have fascinating effects on the
correctness of system operation.  Before we start enabling the userland
daemon automatically, we should fix those problems.  These include at
least:

(1) Incorrect management of credentials such that a surprising set of
    processes and related objects gain root privilege during potentially
    blocking operations.

(2) The /var/run/lock fifo is looked up using the current process's
    working/root directory, so if you have chroot'd processes, you might
    get unexpected results.  For example, if you chroot a user to their
    home directory, locking won't work, but if they're not chrooted, it
    will.  I won't speculate on the correctness of running multiple
    rpc.lockd's. :-)

I'm willing to work on (1) (and have some patches that begin to address
the problem), but (2) will probably require some re-writing to address, as
well as possibly some experimentation to determine the scope of the
problem. 

Robert N M Watson             FreeBSD Core Team, TrustedBSD Project
robert@fledge.watson.org      NAI Labs, Safeport Network Services




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1011019154254.72418C-100000>