Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 beta 3/9/83; site vaxine.UUCP
Path: utzoo!linus!vaxine!ptw
From: ptw@vaxine.UUCP (P. T. Withington)
Newsgroups: net.unix-wizards
Subject: using cu for ct
Message-ID: <315@vaxine.UUCP>
Date: Thu, 1-Sep-83 08:58:38 EDT
Article-I.D.: vaxine.315
Posted: Thu Sep  1 08:58:38 1983
Date-Received: Thu, 1-Sep-83 17:00:44 EDT
Organization: Automatix Inc., Billerica, MA
Lines: 23


Either r got your address wrong or your mailer doesn't know where you are; but
I did try to mail this rather than post it:

     >From ima!vaxine!ptw Tue Aug 30 17:39:47 1983 remote from allegra
     Sender: ptw@ima!vaxine.UUCP
     Subject: cu for ct
     To: lauren@LBL-CSAM

     I have successfully used the following in a shell file to call myself on
     a dialer line that has an init/getty hanging in open.

	     cu $number -t -a /dev/cua0 -l /dev/null < /dev/null

     -t almost does what you want, but specifying /dev/null as the line keeps
     it from complaining "line busy" because init resets the tty modes; using
     /dev/null as input just gets the cu to terminate right away so that it
     doesn't waste cpu cycles.

				  't`   --Tucker (ptw@vaxine.UUCP)
				   ~
P.S.
I'd be interested in ct for 4.1 if you do it.