From owner-freebsd-questions@FreeBSD.ORG Mon Nov 3 13:44:00 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3418A16A4CF for ; Mon, 3 Nov 2003 13:44:00 -0800 (PST) Received: from be-well.no-ip.com (lowellg.ne.client2.attbi.com [66.30.200.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7BF7E43FE1 for ; Mon, 3 Nov 2003 13:43:59 -0800 (PST) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: by be-well.no-ip.com (Postfix, from userid 1147) id 0897D3B05; Mon, 3 Nov 2003 16:43:58 -0500 (EST) Sender: lowell@be-well.ilk.org To: "David Jenkins" References: <002c01c3a252$34e95230$0207a8c0@theta> From: Lowell Gilbert Date: 03 Nov 2003 16:43:58 -0500 In-Reply-To: <002c01c3a252$34e95230$0207a8c0@theta> Message-ID: <447k2hf7q9.fsf@be-well.ilk.org> Lines: 52 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-questions@freebsd.org Subject: Re: Unable to delete empty directory /var/tmp/temproot X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2003 21:44:00 -0000 "David Jenkins" writes: > >On Mon, 3 Nov 2003, David Jenkins wrote: > > > > >I have also tried: > > > > # chflags noschg empty/ > > chflags: empty/: Operation not permitted > > chflags: empty/: Operation not permitted > > > > # chmod -R 0700 empty/ > > chmod: empty/: Operation not permitted > > > > Please could someone point me in the right direction with this. > > > > > >You raised the security level. Immutable flag can't be removed if > >securelevel > 0. > > >Boot into single user mode, then chflags noschg empty/ > > > > Fer > > I booted to single user mode from the boot prompt, but was unable to do > anything inside var because there were no directories there!? You have to mount them first. This is covered in the FAQ. > So, I booted to full mode then did > > # init 1 > > Here, I tried as you suggested but yet again I got the same error. > > Also, when I boot up I have kern_securelevel="0" set in my rc.conf, > which is not > 0 Quoting the Fine Manual: If the security level is initially nonzero, then init leaves it unchanged. Otherwise, init raises the level to 1 before going multi-user for the first time. Since the level cannot be reduced, it will be at least 1 for subsequent operation, even on return to single-user. If a level higher than 1 is desired while running multi-user, it can be set before going multi-user, e.g., by the startup script rc(8), using sysctl(8) to set the ``kern.securelevel'' variable to the required secu- rity level.