From owner-freebsd-questions@FreeBSD.ORG Tue May 29 01:17:39 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A55A2106566C for ; Tue, 29 May 2012 01:17:39 +0000 (UTC) (envelope-from garya@dreamchaser.org) Received: from nightmare.dreamchaser.org (nightmare.dreamchaser.org [12.32.44.142]) by mx1.freebsd.org (Postfix) with ESMTP id 6D3518FC15 for ; Tue, 29 May 2012 01:17:39 +0000 (UTC) Received: from breakaway.dreamchaser.org (breakaway.dreamchaser.org. [12.32.36.73]) by nightmare.dreamchaser.org (8.13.6/8.13.6) with ESMTP id q4T1Hc7B035767 for ; Mon, 28 May 2012 19:17:38 -0600 (MDT) (envelope-from garya@dreamchaser.org) Message-ID: <4FC423B2.7020708@dreamchaser.org> Date: Mon, 28 May 2012 19:17:38 -0600 From: Gary Aitken User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120528 Thunderbird/12.0.1 MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <201205282108.q4SL8fqJ090973@mail.r-bonomi.com> In-Reply-To: <201205282108.q4SL8fqJ090973@mail.r-bonomi.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (nightmare.dreamchaser.org [12.32.36.65]); Mon, 28 May 2012 19:17:38 -0600 (MDT) Subject: Re: removing /var/empty on a non-system disk X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 May 2012 01:17:39 -0000 On 05/28/12 15:08, Robert Bonomi wrote: >> From owner-freebsd-questions@freebsd.org Mon May 28 14:10:55 2012 >> Date: Mon, 28 May 2012 13:05:45 -0600 >> From: Gary Aitken >> To: Polytropon >> Cc: freebsd-questions@freebsd.org >> Subject: Re: removing /var/empty on a non-system disk >> >> On 5/25/2012 4:01 PM, Polytropon wrote: >>> >>> I should have mentioned that I did the (successful) test >>> logging in as root (real console login). If you use "su -" >>> or "su root", the effect should be the same. You can always >>> check the success of your operation with the "ls -lo" command. >> >> Nope. That was the problem. I had logged in on the vty as normal user >> and done su root. Had to back all the way out and log in on the vty as >> root to make it work. > > I'm going to guess that you did 'su root', not 'su - root'. The two commands > are *NOT* identical. 'su root' does not run the root 'login' scripts; thus > environment variables (including path, user, logname etc.) are *not* set as > they are on root login -- this causes some 'am i root' tests to fail. OTOH, > 'su - root' should be equivalent to a root login in all respects. Thank you. That explains a number of problems I've been having. doh. > NOTE; there will be issues if the 'working directory' of a parent process is > the directory you are trying to delete. knew about that part