Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 2 Mar 2004 11:01:25 -0500 (EST)
From:      Robert Watson <rwatson@FreeBSD.org>
To:        Melvyn Sopacua <freebsd-current@webteckies.org>
Cc:        current@FreeBSD.org
Subject:   Re: vipw: pw_tmp(): Operation not permitted
Message-ID:  <Pine.NEB.3.96L.1040302110007.4906B-100000@fledge.watson.org>
In-Reply-To: <200403021659.16782.freebsd-current@webteckies.org>

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

On Tue, 2 Mar 2004, Melvyn Sopacua wrote:

> On Tuesday 02 March 2004 14:08, Erik U. wrote:
> 
> > I get this weird error when i try executing vipw:
> > [root@koti] /home/erik $ vipw
> > vipw: pw_tmp(): Operation not permitted
> > [root@koti] /home/erik $
> 
> Operation not permitted is something else then 'permission denied'.
> Permission denied is related to file and network permissions. Operation
> not permitted relates to operations which are disabled in the kernel or
> by flags on files (see chflags(1)). What's the output of:  sysctl
> kern.securelevel

Sounds like it could well be a file locking problem.  Is rpc.lockd running
on both sides, or alternatively, can the file system be mounted using -L
so as to use local-only locking similar to 4.x? 

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert@fledge.watson.org      Senior Research Scientist, McAfee Research




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