Re: ~uucp broken after 3.5->4.0.3 upgrade

Article View: comp.sys.sun

Article #1595

#1595

From: Mark Lawrence
Date: Fri, 15 Sep 1989 21:26

14 lines
1144 bytes

> 
>     Since we've upgraded to 4.0.3, when people try to uucp to our public
>     directory (e.g., drd!~uucp), they get a remote path permission denied
>     message.[...]

The problem *was* with the USERFILE (although, for the life of me, I don't
understand why...).  We used to have two lines in the USERFILE declaring
/usr/spool/uucppublic and /var/spool/uucppublic as world readable/writeable,
just like the example in the reference section on uucp in the book (page
529).  We combined both paths on one line and the problem goes away.  Go 
figure...

   mark@DRD.Com                (918) 743-3013              Jer. 9:23,24
   {uunet,rutgers}!drd!mark

Technical Details

Message-ID: <8909152126.AA04030@DRD.Com>

Path: arc1-ca.pugleaf.net!utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: mark@drd.com (Mark Lawrence)
Newsgroups: comp.sys.sun
Subject: Re: ~uucp broken after 3.5->4.0.3 upgrade
Keywords: Networks
Message-ID: <8909152126.AA04030@DRD.Com>
Date: 15 Sep 89 21:26:35 GMT
Sender: root@rice.edu
Organization: DRD Corporation, Tulsa, Ok.
Lines: 14
Approved: Sun-Spots@rice.edu
X-Sun-Spots-Digest: Volume 8, Issue 136, message 2 of 13