Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucsd!nprdc!malloy
From: malloy@nprdc.arpa (Sean Malloy)
Newsgroups: comp.unix.questions
Subject: Re: uudecode - permission denied
Message-ID: <2944@skinner.nprdc.arpa>
Date: 21 Jul 89 17:16:23 GMT
References: <1250@servax0.essex.ac.uk> <26040@agate.BERKELEY.EDU>
Reply-To: malloy@nprdc.arpa (Sean Malloy)
Organization: Navy Personnel R&D Center, San Diego
Lines: 29

In article <26040@agate.BERKELEY.EDU> ked@garnet.berkeley.edu (Earl H. Kinmonth) writes:
>In article <1250@servax0.essex.ac.uk> peter@essex.ac.uk writes:
>>Can someone please explain what I/we are doing wrong?
>>I find that to get uudecode to work, the file that I expect it
>>to create must already exist and have the 020 bit set in its mode.
>>Or uudecod states "file: Permission denied"

>Whether it is correct or not, that's the way it works on the SUN I use.
>Fortunately, the uuencode/uudecode source code is readily available
>without this particular "feature" of the SUN implementation.  Get a copy
>of the code, compile it, and place it in a directory where it will be
>found ahead of the system uuencode/decode.

I had the same problem on our Suns, and after a little looking around,
discovered that uudecode is setUID to 'uucp' -- which can't write into
your directories to create the uudecoded file, so you get the file
create failure.

What I wound up doing was making one directory where all the uuencoded
files got stored, which had its permission value set to 777. Uudecode
is perfectly happy writing files into it, and aside from having the
file owned by uucp, everything is fine.


 Sean Malloy					| "The proton absorbs a photon
 Navy Personnel Research & Development Center	| and emits two morons, a
 San Diego, CA 92152-6800			| lepton, a boson, and a
 malloy@nprdc.navy.mil				| boson's mate. Why did I ever
						| take high-energy physics?"