Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!mcgill-vision!snorkelwacker!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!usc!ucsd!pacbell.com!pacbell!premenos!mtdiablo!rob
From: rob@mtdiablo.Concord.CA.US (Rob Bernardo)
Newsgroups: comp.mail.uucp
Subject: CALLBACK in HoneyDanBer workaround
Message-ID: <1990Aug16.013034.11398@mtdiablo.Concord.CA.US>
Date: 16 Aug 90 01:30:34 GMT
Reply-To: rob@mtdiablo.Concord.CA.US (Rob Bernardo)
Organization: Mt. Diablo Software Solutions
Lines: 26

A while back I wrote that the CALLBACK feature in HoneyDanBer uucp (at
least under SUN OS 4.1) was failing.  I wrote that when a remote system,
which is noted in the Permissions file as subject to CALLBACK, logs in
for uucp, my system did not create a C.  file, which meant that if the
immediate call back failed for one or other reason, my system had no way
of keeping track that a call back was still due.

It turns out that uucico does create the C. file, but in the wrong directory!!

I use the following shell script, which I run under cron just prior to
uudemon.hour, to move any C. files to the proper directory.

uucpdir=/usr/spool/uucp
for system in `uuname`
do
    shortname=`echo $system | sed -e 's/^\(.......\).*$/\1/'`
    if [ -f $uucpdir/C.${shortname}* ]
    then
	mv $uucpdir/C.${shortname}* $uucpdir/$system
    fi
done
-- 
Rob Bernardo, Mt. Diablo Software Solutions
"If the world were a logical place, men would ride sidesaddle." Rita Mae Brown
email: rob@mtdiablo.Concord.CA.US
phone: (415) 827-4301