Date: Mon, 10 Nov 1997 10:48:39 -0700 (MST) From: "Thomas S. Traylor" <ttraylor@titan.mcit.com> To: Nadav Eiron <nadav@barcode.co.il> Cc: Thomas.Traylor@mci.com, sporkl@dti.net, Michael Richards <026809r@dragon.acadiau.ca>, freebsd-chat@FreeBSD.ORG Subject: Re: Crashing FreeBSD Message-ID: <Pine.OSF.3.96.971110104336.8311A-100000@titan.mcit.com> In-Reply-To: <Pine.BSF.3.91.971110193644.4123A-100000@gatekeeper.barcode.co.il>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 10 Nov 1997, Nadav Eiron wrote:
>
>
> On Mon, 10 Nov 1997, Thomas S. Traylor wrote:
>
> > On Sun, 9 Nov 1997, sporkl wrote:
> >
> > > Well, there are other ways too.
> > >
> > > 1. Toggle power really fast
> > > 2. write a "forkbomb":
> > > #include <stdio.h>
> > >
> > > main() {
> > >
> > > for(;;) {fork();}
> > > }
> > >
> >
> > This looks like something a student did to us on a VMS system. For
> > those with VMS systems around try:
> >
> > $! bomb.com
> > $!
> > $ spawm/nowait bomb.com
> > $ submit bomb.com
> > $ @bomb.com
>
> moved to -chat
Good idea....
>
> Just like on FreeBSD, VMS can limit the numebr of processes a user can
> have (and can even separatly limit detached, batch and interactive
> processes). All you have to do is set up your sysuaf properly...
This didn't cause the system to crash (it slowed it down a bit). It
did cause us to reboot though.
A reboot was the only real way to clean it up. There were to many
process to kill off. Everytime you killed off a process, it allowed
another process for that user to startup.
Tom
>
> On the other hand, I remember crashing a VAX/VMS 5.2 ( :-) ) by calling
> sys$getjpi with a process name that contained colons (this was later
> fixed in some DEC patch, can't recall which).
>
> >
> > Tom
> >
> Nadav
>
--
Thomas Traylor
Thomas.Traylor@mci.com
ttraylor@titan.mcit.com
(719) 535-1269
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.OSF.3.96.971110104336.8311A-100000>