From:	CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX" 12-DEC-1989 19:42
To:	MRGATE::"ARISIA::EVERHART"
Subj:	Re: Two questions: VAX Notes & ACL's

Received: From UCBVAX.BERKELEY.EDU by GIZMO.SRI.COM with TCP; Tue, 12 DEC 89 10:57:45 PDT
Received: by ucbvax.Berkeley.EDU (5.61/1.40)
	id AA03750; Tue, 12 Dec 89 10:43:35 -0800
Received: from USENET by ucbvax.Berkeley.EDU with netnews
	for info-vax@kl.sri.com (info-vax@kl.sri.com)
	(contact usenet@ucbvax.Berkeley.EDU if you have questions)
Date: 12 Dec 89 18:21:39 GMT
From: shlump.nac.dec.com!cheese.enet.dec.com!kaiser@decwrl.dec.com
Organization: DEC Systems Consulting Group
Subject: Re: Two questions: VAX Notes & ACL's
Message-Id: <6829@shlump.nac.dec.com>
Sender: info-vax-request@kl.sri.com
To: info-vax@kl.sri.com

In article <8912112336.AA29878@ucbvax.Berkeley.EDU>, CADS_COLE@GALLUA.BITNET
("Kevin Cole at Gallaudet U. Washington DC") writes...

>First, what would cause the NOTE$NOTEBOOK.NOTES file to grow quickly?  Several
>users are noticing an alarming growth in the file size, while others subscribed
>to the same conferences, are noticing almost no change in the file size.

Large UNSEEN counts, for one thing.  You can shrink a notebook pretty easily,
for instance with this code, which I use as SHRINK.COM:

	$ V = F$VERIFY(1)
	$ ON ERROR THEN GOTO EXIT
	$ ANALYZE /RMS /FDL /OUT='P1'.FDL	'P1'.NOTE
	$ EDIT /FDL /NOINTER /ANAL='P1'.FDL	'P1'.FDL 
	$ CONVERT /FDL='P1'.FDL 'P1'.NOTE	'P1'.NOTE
	$ DELETE 'P1'.FDL;*
	$ EXIT:
	$ V = 'F$VERIFY(V)

The thoughtful sysadmin of a system with lots of naive users with large
notebooks might set up a job to run periodically to do this for all of them.
Invoke it, for instance, like

	$ @SHRINK NOTE$NOTEBOOK

Then delete earlier versions if you're satisfied with the results.

>Second question:  If I keep the (S,O,G,W) protections fairly low, and create an
>ACL with ACCESS=NONE for a particular userid, will it block them out?  There
>are several open conferences on the system, and recently a group of moderators
>have been discussing how to handle "problem" users.  I thought the ideal
>solution was to limit or completely eliminate their access via an ACL.  So what
>I want is a simple way to create a situation where "everybody except the
>following group" has READ+WRITE access to a file.

Make the conferences available only via the server, and set up the server with
its own account, making sure with ACLs that only the server can have access to
the conferences.  Then make the conferences members-only.  Administering a
members-only conference isn't hard, and the point will be made.

Then give them their own conference to blow off steam.

---Pete

kaiser@cheese.enet.dec.com
DEC, 2 Mt. Royal Ave. (UPO1-3), Marlboro MA 01752-9108
508-480-4345 (machine: 617-641-3450)