Newsgroups: news.software.b
Path: utzoo!henry
From: henry@utzoo.uucp (Henry Spencer)
Subject: Re: How do I issue a "sendme" control message? (really Cnews & file systems)
Message-ID: <1989Jul19.155013.17932@utzoo.uucp>
Organization: U of Toronto Zoology
References: <749@icus.islp.ny.us> <1989Jul18.154058.2638@dlb.uucp> <1989Jul19.044308.1646@tmsoft.uucp>
Date: Wed, 19 Jul 89 15:50:13 GMT

In article <1989Jul19.044308.1646@tmsoft.uucp> mason@tmsoft.UUCP (Dave Mason) writes:
>We haven't installed the new release yet because they put in.coming in
>the article file system & it seems to be hardcoded too many places to
>quickly change it to the lib file system.  It should be a seperate
>define, setup up BY DEFAULT however they wish.

Sigh, you can please some of the people some of the time...  We had many
more people complaining about putting in.coming under the control files,
because it can get big and people would like to put all the big varying
space demands under /usr/spool. 

And we wanted to hold down the number of magic environment variables.
There are already seven of them.  We could probably have doubled that
number without much effort, but seven already struck us as rather a lot.

There are not that many places that know the name of in.coming; a quick
grep will find them all.  Obviously the input subsystem and nntp know about
it.  Build knows about creating the directory, spacefor knows about
finding free space in it, newsdaily knows where to look for signs of input
problems, and newsboot knows where to clean up the mess on reboot.  That's it.
-- 
$10 million equals 18 PM       |     Henry Spencer at U of Toronto Zoology
(Pentagon-Minutes). -Tom Neff  | uunet!attcan!utzoo!henry henry@zoo.toronto.edu