Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!CIM-VAX.HONEYWELL.COM!thompson%animal.decnet
From: thompson%animal.decnet@CIM-VAX.HONEYWELL.COM ("ANIMAL::THOMPSON")
Newsgroups: comp.sys.apollo
Subject: Re: Protection in Internets (lprotect)
Message-ID: <8906122032.AA19523@umix.cc.umich.edu>
Date: 12 Jun 89 21:09:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 16

Aaarrggghhh.

We were told, when SR10.1 came out to us, NOT, REPEAT NOT, to use the
'lprotect' command lest horrible nasty things happen to us.  As I
understood (understand) it, lprotect is buggy, and may prevent normal
root processes from functioning.  (Trivial things like init, tcpd, dm, ....)
What's the scoop?  Was it changed, and we weren't told?  Or are we being
given bad, dangerous information now?

For what it's worth, the spm access control file works just fine.

John Thompson
Honeywell, SSEC
12001 St Hwy 55
Plymouth, MN,  55441
The above ramblings are my own, and have little if any bearing on my employer.