From owner-freebsd-stable@FreeBSD.ORG Mon Nov 1 19:48:08 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 390AF16A4CE for ; Mon, 1 Nov 2004 19:48:08 +0000 (GMT) Received: from smtp-gw-cl-c.dmv.com (smtp-gw-cl-c.dmv.com [216.240.97.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id A13D043D1D for ; Mon, 1 Nov 2004 19:48:07 +0000 (GMT) (envelope-from sven@dmv.com) Received: from lanshark.dmv.com (lanshark.dmv.com [216.240.97.46]) by smtp-gw-cl-c.dmv.com (8.12.10/8.12.10) with ESMTP id iA1JrC1P068663 for ; Mon, 1 Nov 2004 14:53:12 -0500 (EST) (envelope-from sven@dmv.com) From: Sven Willenberger To: freebsd-stable@freebsd.org In-Reply-To: <20041101173050.GA66108@xor.obsecurity.org> References: <148cabbc04103117195de9fe4e@mail.gmail.com> <20041101173050.GA66108@xor.obsecurity.org> Content-Type: text/plain Date: Mon, 01 Nov 2004 14:49:48 -0500 Message-Id: <1099338588.24107.19.camel@lanshark.dmv.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.0 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.39 Subject: Re: Why the mode of /dev/null is changed after system reboot? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Nov 2004 19:48:08 -0000 On Mon, 2004-11-01 at 09:30 -0800, Kris Kennaway wrote: > On Mon, Nov 01, 2004 at 09:19:12AM +0800, Iva Hesy wrote: > > I have a gateway running FreeBSD 4.10-p3. Normally, the mode of > > /dev/null should be 666, but recently, I find that its mode is changed > > to 600 automatically after reboot, I have checked all /etc/rc* and > > /usr/local/etc/rc.d/*, but I can't get anything that led to it...:-( > > Probably a local error. Try changing scripts to #!/bin/sh -x and > carefully watch (or log) the boot process. Start with any local > scripts you have since it's most likely to be a problem there. > > Kris Actually I have found this happening on my 4.10 boxen as well. I thought it was some one-time glitch and just chmodded the thing back. Didn't even think about it until I saw this post. I will try to see if I can catch the circumstances surrounding it if it happens again.