Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!husc6!cmcl2!brl-adm!adm!bzs@bu-cs.bu.EDU
From: bzs@bu-cs.bu.EDU (Barry Shein)
Newsgroups: comp.unix.wizards
Subject: Determining the max number of open files on System V
Message-ID: <7895@brl-adm.ARPA>
Date: Wed, 17-Jun-87 12:07:17 EDT
Article-I.D.: brl-adm.7895
Posted: Wed Jun 17 12:07:17 1987
Date-Received: Sun, 21-Jun-87 15:26:30 EDT
Sender: news@brl-adm.ARPA
Lines: 20


John Haugh responding to my note:
>Don't fork - please.  I believe there are no fewer than 2 forks() per
>system(3) call, and a 68000 machine can only handle 30 or so per second,
>depending on the size of the module.
>
>- John.

Gee, then I assume you can code more than 30 /dev/kmem grovelers per
second and fix them just as quick on each change to the OS? Port them
to machines that don't support a /dev/kmem? A microbuck saved is a
microbuck earned I suppose.

I also assume this means you are recommending against shell scripts
and pipes and all that nonsense, just litters the system with lots of
fork/execs, feh! Better everyone on the system just programs
everything themselves, maybe we should delete everything but an editor
and the C compiler.

	-Barry Shein, Boston University