Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!ucbvax!agate!ziploc!eps
From: eps@toaster.SFSU.EDU (Eric P. Scott)
Newsgroups: comp.sys.next
Subject: Re: PLEASE HELP!!! Problem with running WriteNow
Message-ID: <1071@toaster.SFSU.EDU>
Date: 22 Dec 90 05:03:27 GMT
References: <1990Dec20.161254.1@linus.claremont.edu> <1990Dec21.184328.1@linus.claremont.edu>
Reply-To: eps@cs.SFSU.EDU (Eric P. Scott)
Organization: San Francisco State University
Lines: 11

In article <1990Dec21.184328.1@linus.claremont.edu>
	jack@linus.claremont.edu writes:
>I found my mistake.  For future refence the /private/spool and the /private/tmp
>should have 777 protection on them.

Is this some new 2.0 breakage?  What does WriteNow need in
/private/spool, and why can't /tmp be 1777?

(I assume I don't need to explain why 777 is a security hole.)

					-=EPS=-