mark@drd.com (Mark Lawrence) (09/16/89)
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. uucp is defined in the passwd file with a home dir of
/var/spool/uucppublic. The USERFILE has /usr/spool/uucppublic and
/var/spool/uucppublic entries as world accessible. If folks uucp to
drd!/usr/spool/uucppublic, it works just fine. Anybody know the
magic incantation that gets the ~uucp reference working again?
--
mark@DRD.Com (918) 743-3013 Jer. 9:23,24
{uunet,rutgers}!drd!markmark@drd.com (Mark Lawrence) (09/16/89)
> > 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