Date: Mon, 25 Nov 1996 18:38:38 +0100 (MET) From: sos@FreeBSD.org To: jgreco@brasil.moneng.mei.com (Joe Greco) Cc: mtaylor@cybernet.com, hackers@FreeBSD.org Subject: Re: Hang your machine with ScrollLock Message-ID: <199611251738.SAA10053@ravenock.cybercity.dk> In-Reply-To: <199611251650.KAA15011@brasil.moneng.mei.com> from "Joe Greco" at Nov 25, 96 10:50:05 am
next in thread | previous in thread | raw e-mail | index | archive | help
In reply to Joe Greco who wrote:
>
> > Here's a good one I did the other day (by accident):
> >
> > I have a cron job that runs every two minutes to display the
> > uptime on the console (to make sure that it keeps scrolling)
> > on the company's name server (uptime > /dev/console).
> >
> > I put the console in scroll-lock mode by accident. About
> > 0.5 hours later, name resolving was dead. I went to the
> > name server machine and saw about 20 or so of these 'uptime'
> > processes running, waiting to output to the console. So many
> > of these were running (along with CRON processes and sh processes)
> > that the system could not create more processes (as the syslog
> > told me).
> >
> > As soon as I hit the scroll-lock key, everything was fine-
> > all of the uptime processes completed, and name serving
> > went on as usual.
I belive this to be fixed in what was 2.2-current long ago...
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team
Even more code to hack -- will it ever end
..
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611251738.SAA10053>