warren@pluto.UUCP (Warren Burstein) (04/16/87)
It seems that if uucico has called another system before the calling window ended, it keeps on talking past the end of the window. Does anyone have any ideas to solve this? Patches, kludges, whatever. thanks -- warren /|/~\~~\ Why doesn't life come with subtitles? |__/__/_/ | seismo!philabs!tg!pluto!warren /
romain@pyrnj.uucp (Romain Kang) (04/20/87)
I'm not sure I know what you mean by calling window. Do you mean
calls that last beyond the times permitted in L.sys? If that's the
case, then you could write a program that looked in the lock files
for forbidden systems. For example, if you don't want to talk to
"okstate" after 0700, the program might be invoked from cron as
killuucp okstate
killuucp would look like
LOCKDIR=/usr/spool/uucp # salt to taste
cd $LOCKDIR
for system
do
if [ -f LCK..${system} ] ; then
kill `getlockpid LCK..${system}`
fi
done
and getlockpid would look like
/* v7, bsd, 5.0, but not honey danber */
main(argc,argv)
int argc; char **argv;
{
int fd, pid;
while (*++argv)
if ((fd = open(*argv, 0)) > 0) {
read(fd, (char *)&pid, sizeof(int));
printf("%d\n", pid);
}
}
Oh well, you get the idea...
Unfortunately, that's not a very graceful way to shut off uucp. If
you've gotten 90% of a 1MB file through, you might prefer to let it
finish. In that case, there's no uucico that I know of that provides
for that sort of graceful shutdown. (4.3 uucico will turn itself
off if it sees an /etc/nologin, but that blocks your human users...)
--
Romain Kang {allegra,cmcl2,mirror,pyramid,rutgers}!pyrnj!romain
Pyramid Technology Corp. / 10 Woodbridge Center. Dr / Woodbridge, NJ 07095
"Now for a version of expire that runs on my kitchen memo board..."