Xref: utzoo comp.unix.xenix:3260 comp.bugs.sys5:547
Path: utzoo!attcan!uunet!fsc2086!jim
From: jim@fsc2086.UUCP (Jim O'Connor)
Newsgroups: comp.unix.xenix,comp.bugs.sys5
Subject: Re: Fatal bug in uucico
Summary: uucp and uux should be setuid uucp
Message-ID: <179@fsc2086.UUCP>
Date: 8 Sep 88 18:15:36 GMT
References: <6293@rpp386.Dallas.TX.US>
Sender: jim@fsc2086.UUCP
Lines: 24

In article <6293@rpp386.Dallas.TX.US>, jfh@rpp386.Dallas.TX.US (The Beach Bum) writes:
> I'm not certain this is limited to SCO Xenix, hence the cross-post.
> 
> If there are UUCP files in /usr/spool/uucp which are not readable
> by uucico, uucico will hang in a loop continuously re-reading the
> spool directory scanning for work.
> 
> Changing the ownership of all UUCP files in the spool directory to the
> owner of uucico will correct the problem.  . . .

The programs "uucp" and "uux" should be setuid to your uucp user (usually uucp).
This way, whenever uucp or uux create a work file in /usr/spool/uucp
it will be assured to have the owner id of the uucicio process (which should
also be setuid uucp).
Just run 

# cd /usr/bin
# chown uucp uucp uux
# chmod 4711 uucp uux
# cd /usr/lib/uucp
# chown uucp uucico
# chmod 4711 uucico

To make sure those files are all in agreement.