From owner-freebsd-stable@FreeBSD.ORG Tue Nov 2 06:08:25 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 1E3FA16A4CE for ; Tue, 2 Nov 2004 06:08:25 +0000 (GMT) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6474943D49 for ; Tue, 2 Nov 2004 06:08:24 +0000 (GMT) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.13.1/8.13.1) with ESMTP id iA268FQU089251; Tue, 2 Nov 2004 09:08:15 +0300 (MSK) (envelope-from marck@rinet.ru) Date: Tue, 2 Nov 2004 09:08:15 +0300 (MSK) From: Dmitry Morozovsky To: Sven Willenberger In-Reply-To: <1099338588.24107.19.camel@lanshark.dmv.com> Message-ID: <20041102090724.K88773@woozle.rinet.ru> References: <148cabbc04103117195de9fe4e@mail.gmail.com> <1099338588.24107.19.camel@lanshark.dmv.com> X-NCC-RegID: ru.rinet MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org 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: Tue, 02 Nov 2004 06:08:25 -0000 On Mon, 1 Nov 2004, Sven Willenberger wrote: SW> > > I have a gateway running FreeBSD 4.10-p3. Normally, the mode of SW> > > /dev/null should be 666, but recently, I find that its mode is changed SW> > > to 600 automatically after reboot, I have checked all /etc/rc* and SW> > > /usr/local/etc/rc.d/*, but I can't get anything that led to it...:-( SW> > SW> > Probably a local error. Try changing scripts to #!/bin/sh -x and SW> > carefully watch (or log) the boot process. Start with any local SW> > scripts you have since it's most likely to be a problem there. SW> SW> Actually I have found this happening on my 4.10 boxen as well. I thought SW> it was some one-time glitch and just chmodded the thing back. Didn't SW> even think about it until I saw this post. I will try to see if I can SW> catch the circumstances surrounding it if it happens again. I remember I stepped into this once or twice in the past. Bad umask at mergemaster/MAKEDEV time possibly? Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------