From owner-freebsd-current@FreeBSD.ORG Tue Mar 2 08:02:34 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF44E16A4CE for ; Tue, 2 Mar 2004 08:02:34 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F80243D1F for ; Tue, 2 Mar 2004 08:02:34 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.10/8.12.10) with ESMTP id i22G1PDL005065; Tue, 2 Mar 2004 11:01:25 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i22G1P2m005062; Tue, 2 Mar 2004 11:01:25 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Tue, 2 Mar 2004 11:01:25 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Melvyn Sopacua In-Reply-To: <200403021659.16782.freebsd-current@webteckies.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@FreeBSD.org Subject: Re: vipw: pw_tmp(): Operation not permitted X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Mar 2004 16:02:34 -0000 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