The original problem was on a 1200 with dual CPUs where the /bin/login
program would hang and not allow any user to log in, FTP, telnet, or
otherwise.. This weekend I was running some tests on our ES40 (v5.0)
and decided that I should login a bunch of times and make sure I set all
the PTYs and kernel parameters were correct allow a couple hundred
users. So I wrote the following script (as a normal user with a proper
.rhosts):
#!/bin/ksh
A=0
while [ $A -le 250 ]; do
rlogin localhost &
(( A = $A + 1 ))
done
After running this script, I opened up a new telnet session to the
machine, and sure enough, the /etc/issue.net was displayed, I was told
what version of Tru64 UNIX it was, and what PTY i was on.. BUT NO
login: prompt!!
I had to go to the console, (luckily I was already logged in), and stop
and restart the prpasswd daemon.
It looks like a prpasswd bug rather than an misconfig on our part, as
the 1200 was an upgrade install, the ES40 was full install and both
exhibit the same problem. I DO have a ticket open with Compaq support,
and I imagine there will be a bugfix soon. I decided to post this now
because our 1200 system is a lightly loaded one, and this problem pops
up almost every day - sometimes twice a day -- so I'm almost sure others
will experience this as well.
--Robert
----Original problem ----
We have recently upgraded serveral of our systems to v5.0. One system
in particular (intermittently) hangs when the login program is called
either at the command line or by telnetd or by ftpd (or any other
daemon). Though our web servers weren't affected...seems like any
server that didn't have to authenticate a password worked...
When you try to telnet in, you get the issue.net file displayed, then
you get the "Tru64 UNIX..... (pts/4)" line displayed, then it hangs.
With FTP, after you enter your username, it hangs.
Received on Sun Oct 03 1999 - 04:00:04 NZDT