From owner-freebsd-chat  Mon Nov 10 09:53:29 1997
Return-Path: <owner-freebsd-chat>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id JAA15099
          for chat-outgoing; Mon, 10 Nov 1997 09:53:29 -0800 (PST)
          (envelope-from owner-freebsd-chat)
Received: from titan.mcit.com (titan.mcit.com [166.37.52.154])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id JAA15083
          for <freebsd-chat@FreeBSD.ORG>; Mon, 10 Nov 1997 09:53:22 -0800 (PST)
          (envelope-from ttraylor@titan.mcit.com)
Received: from localhost by titan.mcit.com (5.65v4.0/1.1.10.5/03Nov97-0335PM)
	id AA08328; Mon, 10 Nov 1997 10:48:39 -0700
Date: Mon, 10 Nov 1997 10:48:39 -0700 (MST)
From: "Thomas S. Traylor" <ttraylor@titan.mcit.com>
Reply-To: Thomas.Traylor@mci.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
In-Reply-To: <Pine.BSF.3.91.971110193644.4123A-100000@gatekeeper.barcode.co.il>
Message-Id: <Pine.OSF.3.96.971110104336.8311A-100000@titan.mcit.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-chat@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

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