Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!cs.utexas.edu!uunet!amgraf!rjmkc!srwic!sralston
From: sralston@srwic.UUCP (Steve Ralston)
Newsgroups: comp.unix.sysv386
Subject: Re: Kermit & UUGETTY
Message-ID: <1991Jun24.013528.9137@srwic.UUCP>
Date: 24 Jun 91 01:35:28 GMT
References: <13256@uwm.edu>
Distribution: usa
Organization: SRS, Wichita, KS
Lines: 33

peter@miller.cs.uwm.edu (Peter J. Diaz de Leon) writes:

> I am running AT&T SYS V 3.2.1 and a Trailblazer T1600.
> UUGETTY is running on the port which the Trailblazer.
>
> What I need is a version of Kermit or some other communication
> program which when invoked kills the uugetty, and allows me
> to connect to the modem and dial out.
>
> Right now if I invoke kermit and connect the login prompt
> scrolls repeatedly accross the screen.

What you need is a version of Kermit which creates the correct *type* of lock
file.  Since AT&T SYS V Release 3 distributes HoneyDanBer UUCP, I would bet
that the version of Kermit you are using is creating a [sysVr2 UUCP style]
binary lock file (4 byte integer) in /usr/spool/uucp instead of a [HDB style]
ascii lock file (11 bytes).

It's been a long while since I looked at the kermit sources, but you I think
you need to recompile it, specifically for sysvr3, or with -DHDBUUCP
(or some such) that tells it you are running HoneyDanBer UUCP.

> The only solution right now is to edit the inittab file and
> comment the line that puts the uugetty on the modem, and
> then kill uugetty.  What I am looking for is something a little
> more automated similar to what CU does to uugetty. 
>
> Any ideas are more than welcome.
>    Thanks 
>    Peter (peter@miller.cs.uwm.edu)
-- 
Steve Ralston    (sralston@srwic.UUCP || ..!uunet!ncrcom!ncrwic!srwic!sralston)
235 N Zelta, Wichita, KS 67206