peter@miller.cs.uwm.edu (Peter J. Diaz de Leon) (06/21/91)
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.
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)cpcahil@virtech.uucp (Conor P. Cahill) (06/21/91)
peter@miller.cs.uwm.edu (Peter J. Diaz de Leon) writes: >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. No. What you need is a kermit that creats a lock file in /usr/spool/lock so that the uugetty knows to leave the line alone (that is how cu does it). The other solution (which is documented in the FAQ) is to use the dual-port feature present in most OSs. This allows you to have a standard getty on a line and use another /dev entry for dial out. the tty driver handles the handshaking and locking internally. -- I guess these are the views of VTI - since it is my consulting company. Conor P. Cahill (703)430-9247 uunet!virtech!cpcahil Virtual Technologies, Inc. 46030 Manekin Plaza Sterling, VA 22170
sralston@srwic.UUCP (Steve Ralston) (06/24/91)
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