can't find tty in protected database

© December 2004 (various authors)

---

What is this stuff?

If this isn't exactly what you wanted, please try our Search (there's a LOT of techy and non-techy stuff here about Linux, Unix, Mac OS X and just computers in general!):

From: Jeff Liebermann <jeffl@comix.santa-cruz.ca.us>
Subject: Re: Long Pause During Login
Date: Tue, 09 Jan 2001 08:35:50 -0800
References: <m14G01r-000COwC@egps.com> 

On Tue, 9 Jan 2001 14:45:39 GMT, Nachman Yaakov Ziskind <awacs@egps.com>
wrote:

>.. starting this morning, having the same problem reported the last
>couple of days in the ng: after entering user name, pause of 27
>seconds, password prompt, and another 27 second pause after entering
>password. Sometimes I get syslog messages: "can't find terminal
>control database entry for line ttypxx", sometimes not. Sometimes the
>login process times out after entering password, sometimes not. Once 
>logged in, the system, the system is its usual wonderful self. No delay 
>on su. All our users are in thru telnet. /etc/hosts is fine.

Y2.001K bug?
Check the permissions on /etc/resolv.conf.  It should be 644 and not 640.
Telnetd insists on doing a reverse DNS lookup on literally every
connection (including local) and requires a DNS server.  You can speed
things up if the DNS server goes down by putting bogus entries for each
of your remote machines in /etc/hosts for each of your pseudo ttys.  The
host names don't need to be real or even sane.  I use like:
        192.168.111.50  bogus50  bogus50.LearnByDestroying.com
        192.168.111.51  bogus51  bogus51.LearnByDestroying.com
        192.168.111.52  bogus52  bogus52.LearnByDestroying.com
        192.168.111.53  bogus53  bogus53.LearnByDestroying.com
        192.168.111.54  bogus54  bogus54.LearnByDestroying.com

The "can't find terminal control database entry for line ttypxx" is
unrelated.  It means that you have more pseudo ttys configured than the
[deleted explative] C2 security abomination has inscribed in its
auth/ttys database.  See:
   https://www.sco.com/cgi-bin/ssl_reference?104588
for the cerimony.

>OS is SCO 5.0.6. Uptime is 76 days. What's a poor attorney to do?

If you're a poor attorney, I suggest a crash course in litigation,
obfuscation, or whatever attorneys normally do, which should make you a
better attorney.  If you've been up for 76 days, I also suggest getting
some sleep.


-- 
Jeff Liebermann   jeffl@comix.santa-cruz.ca.us
150 Felker St #D  Santa Cruz CA  95060
831-421-6491 pager   831-429-1240 fax
https://www.cruzio.com/~jeffl/sco/   SCO stuff

Got something to add? Send me email.

---

Have you tried Searching this site?

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more.

Contact us