Date: Thu, 24 Sep 1998 18:11:00 -0700 From: John Polstra <jdp@polstra.com> To: nathan@rtfm.net Cc: bugs@FreeBSD.ORG Subject: Re: /dev/null breakage in 2.2.7 Message-ID: <199809250111.SAA01139@austin.polstra.com> In-Reply-To: <19980924151459.A14371@binary.net> References: <19980924151459.A14371@binary.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <19980924151459.A14371@binary.net>,
Nathan Dorfman <nathan@rtfm.net> wrote:
> in 2.2.7-S (shortly past 2.2.7-R), reading /dev/null begins producing the
> output of this cron job:
>
> */10 * * * * root /home/nathan/pop3ck mail xxxxxxxxxx@alphame.com 3 > /dev/null 2>&1
>
> nathan@shell.fcc.net:~% cat /dev/null
> Connecting to xxx.xxx.xxx.xxx...connected.
> Read +OK.
>
> Writing nothing to /dev/null makes it work right again:
>
> shell# cat > /dev/null
> shell# cat /dev/null
> shell#
>
> Then,
>
> shell# echo foo > /dev/null
> shell# cat /dev/null
> foo
> shell#
>
> Is my bit bucket overflowing? :-P is this known/fixed in a newer -STABLE?
Do an "ls -l /dev/null" and I'm sure you'll find that it's a regular
file on your system, and not a device as it is supposed to be. It
_should_ look like this:
crw-rw-rw- 1 root wheel 2, 2 Sep 24 17:54 /dev/null
Note the "c" in the first column.
Become root, get into /dev, and type:
rm null
./MAKEDEV std
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Self-knowledge is always bad news." -- John Barth
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809250111.SAA01139>