Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!caip!elbereth!rutgers!lll-crg!seismo!vrdxhq!BMS-AT!stuart
From: stuart@BMS-AT.UUCP (Stuart D. Gathman)
Newsgroups: net.bugs.uucp,net.unix-wizards
Subject: Re: uupick on hp 550 running hp-ux
Message-ID: <251@BMS-AT.UUCP>
Date: Fri, 17-Oct-86 23:20:37 EDT
Article-I.D.: BMS-AT.251
Posted: Fri Oct 17 23:20:37 1986
Date-Received: Tue, 21-Oct-86 22:36:26 EDT
References: <17@cogent.UUCP>
Distribution: net
Organization: Business Management Systems, Inc., Fairfax, VA
Lines: 15
Keywords: lame, helpless, castrated, no fun either
Xref: watmath net.bugs.uucp:809 net.unix-wizards:20033
Summary: same problem here - with fix

In article <17@cogent.UUCP>, mark@cogent.UUCP (Mark Steven Jeghers) writes:

> one received file at a time and asking what to do with it.  THe problem
> is that whenever I tell it where to move the file to, I am told that that
> directory cannot be accessed.

Our SCO Xenix system had the same bug.  The problem is that uupick was
written as a shell script and all the public directories were owned
by uucp with no write permission for 'other'.  I fixed the problem by
changing the permissions on all public directories to 777.  There is still
a problem when new public directories are created, but I can fix those
as they come along.  The real solution is to write a suid version of uupick
in 'C' or to fix whoever creates the default permissions and owners.
-- 
Stuart D. Gathman	<..!seismo!{vrdxhq|dgis}!BMS-AT!stuart>