From owner-freebsd-questions@FreeBSD.ORG Thu Mar 20 16:32:03 2008 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 19DF5106567A for ; Thu, 20 Mar 2008 16:32:03 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from be-well.ilk.org (dsl092-078-145.bos1.dsl.speakeasy.net [66.92.78.145]) by mx1.freebsd.org (Postfix) with ESMTP id DAF898FC12 for ; Thu, 20 Mar 2008 16:32:02 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: by be-well.ilk.org (Postfix, from userid 1147) id 9276C28465; Thu, 20 Mar 2008 12:32:01 -0400 (EDT) To: =?iso-8859-1?Q?Matthias_Gamsj=E4ger?= References: <585602e10803191252s34b244b2lbea6345a52c06dbc@mail.gmail.com> From: Lowell Gilbert Date: Thu, 20 Mar 2008 12:32:01 -0400 In-Reply-To: <585602e10803191252s34b244b2lbea6345a52c06dbc@mail.gmail.com> ("Matthias =?iso-8859-1?Q?Gamsj=E4ger=22's?= message of "Wed\, 19 Mar 2008 20\:52\:49 +0100") Message-ID: <44zlstxsou.fsf@be-well.ilk.org> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-questions@freebsd.org Subject: Re: Missing /dev/null after few min 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: Thu, 20 Mar 2008 16:32:03 -0000 "Matthias Gamsj=E4ger" writes: > I'm running freebsd for couple of years now and never had really big > problems but this one I can't solve on my own. Running releng 7 for 6 mon= ths > now but recently after running X for like 10min the systems is missing > /dev/null. So you can imaging that most programs start complaining about = it. > Right now I recreate it with mknod /dev/null c 1 3 but that's not a real > solution because it starts to disappear again after few minutes. > I'm for 99% sure it's not freebsd problem but more a application problem = but > I wonder if anyone ran into the same trouble after upgrading xyz port? Or > even better has a solution for it? Yep, something is deleting it. Something with permissions to delete it, which shouldn't be many things. First make sure that it has the correct permissions, then check what's running as root. You might be able to find a process that has a file handle open on /dev/null or even on /dev itself, but I'd consider that a long shot.