Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 20 Mar 2008 20:09:52 +0100
From:      "=?ISO-8859-1?Q?Matthias_Gamsj=E4ger?=" <mgamsjager@gmail.com>
To:        freebsd-questions@freebsd.org
Subject:   Re: Missing /dev/null after few min
Message-ID:  <585602e10803201209x11baf803x7b7978a130073e55@mail.gmail.com>
In-Reply-To: <44zlstxsou.fsf@be-well.ilk.org>
References:  <585602e10803191252s34b244b2lbea6345a52c06dbc@mail.gmail.com> <44zlstxsou.fsf@be-well.ilk.org>

next in thread | previous in thread | raw e-mail | index | archive | help
The guilty package seems the be gnash.

On Thu, Mar 20, 2008 at 5:32 PM, Lowell Gilbert <
freebsd-questions-local@be-well.ilk.org> wrote:

> "Matthias Gamsj=E4ger" <mgamsjager@gmail.com> 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
> months
> > now but recently after running X for like 10min the systems is missing
> > /dev/null. So you can imaging that most programs start complaining abou=
t
> it.
> > Right now I recreate it with mknod /dev/null c 1 3 but that's not a rea=
l
> > solution because it starts to disappear again after few minutes.
> > I'm for 99% sure it's not freebsd problem but more a application proble=
m
> 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.
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?585602e10803201209x11baf803x7b7978a130073e55>