Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!iuvax!bsu-cs!dhesi
From: dhesi@bsu-cs.UUCP (Rahul Dhesi)
Newsgroups: comp.unix.questions
Subject: Re: UUCICO exit status...
Message-ID: <1571@bsu-cs.UUCP>
Date: Sun, 22-Nov-87 23:32:42 EST
Article-I.D.: bsu-cs.1571
Posted: Sun Nov 22 23:32:42 1987
Date-Received: Wed, 25-Nov-87 19:57:09 EST
References: <134@csd_v.UUCP>
Reply-To: dhesi@bsu-cs.UUCP (Rahul Dhesi)
Organization: CS Dept, Ball St U, Muncie, Indiana
Lines: 34

In article <134@csd_v.UUCP> bak@csd_v.UUCP (Bruce) writes:
>Perhaps I am reinventing the wheel here, but I am trying to write
>a utility that polls a system and continues to retry every so often
>( default 1 hour intervals ) until a successful connection is established.

If you're using 4.3BSD, use the "uupoll" command to queue a null
request, and invoke uucico hourly from cron.

If you're using System V Release 2, create a uupoll script that
includes the following lines:

     pollfile=/usr/spool/uucp/C.${system}ACPOLL
     touch $pollfile && chmod a+w $pollfile

Here, the variable "system" contains the name of the system for which
you wish to queue a null request.

(My uupoll script actually validates the system name against those
returned by the uuname command, so a mistyped system name doesn't cause
trouble.)

Invoke this uupoll script when you want to queue a null request.  Then
whenever uucico is invoked it will attempt to call the system, and will
keep on doing so until the connection is successful.

Also, since you will be invoking uucico hourly, you may wish to add the
-r flag to all uucp requests, so they are all queued instead of
invoking uucico immediately.  (This flag may be undocumented for some
commands.)  If you are using smail, add the -r flag to where it calls
uux.

I don't know how System V Release 3 handles this.
-- 
Rahul Dhesi         UUCP:  <backbones>!{iuvax,pur-ee,uunet}!bsu-cs!dhesi