Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!decwrl!shlump.dec.com!ryn!decvax!ima!cfisun!lakart!dg From: dg@lakart.UUCP (David Goodenough) Newsgroups: comp.unix.questions Subject: Re: What's wrong with my inittab? Message-ID: <594@lakart.UUCP> Date: 26 Jun 89 15:01:49 GMT References: <2048@csuna.csun.edu> Organization: Lakart Corporation, Newton, MA Lines: 52 abcscnge@csuna.csun.edu (Scott "The Pseudo-Hacker" Neugroschl) sez: > I have a VME bus box running System V. I have 18 serial ports: > (/dev/console, /dev/tty01, /dev/tty[12][1-8]). On /dev/tty18, > I have a direct connection (via genderchangers/nullmodems) to a > true blue AT 339 running SCO Xenix/286 2.2.1. (the VME serial > ports are MVME332XT boards). > > Here's the problem: I have uugetty running in my inittab on tty18. > ps -ef shows NO associated terminal for the uugetty, i.e. > > $ ps -ef > UID PID PPID C STIME TTY TIME COMMAND > ... > root 27303 1 0 00:43:47 ? 0:00 /etc/uugetty -r -t 60 tty18 9600 > ... > > Other uugettys or straight gettys (tty17, or tty27, for example) have > the correct associated tty. The problem is that the AT can't call up > the VME box for UUCP purposes, because no login prompt is received. Hummmm. Sounds a bit like our ISI running BSD 4.3. Here's some output from a ps ax: PID TT STAT TIME COMMAND ....... 160 ? I 0:00 - std.9600 ttyh0 (/etc/getty) 163 ? I 0:00 - std.9600 ttyh3 (/etc/getty) 165 ? I 0:00 - std.9600 ttyh5 (/etc/getty) 166 ? I 0:00 - std.9600 ttyh6 (/etc/getty) ....... 173 ? I 0:00 - A2400 ttydx (/etc/getty) 158 co I 0:00 - std.9600 console (/etc/getty) 161 h1 I 0:00 - std.9600 ttyh1 (/etc/getty) 162 h2 I 0:00 - std.9600 ttyh2 (/etc/getty) ....... Odd that. Well it just so happens that the console, ttyh1, and ttyh2 are the only ports with terminals plugged in (except ttyh4, where I am right now :-) ). So I'm guessing (comments anyone) that the getty doesn't print a prompt or "attach" itself till after CD rises. Note that ttydx is attached to our modem, which currently is hung up. Try getting one of those serial line monitor widgets from Radio Shack, plug it in, and see what you have where. _POSSIBLY_ looping 20 (DTR) to 8 (CD) will work, although it may have unpleasnt side effects if the getty is always awake (in particular calling out may get a bit touchy). Also check pin 6 (DSR), you might need to loop there, rather than pin 8. -- dg@lakart.UUCP - David Goodenough +---+ IHS | +-+-+ ....... !harvard!xait!lakart!dg +-+-+ | AKA: dg%lakart.uucp@xait.xerox.com +---+