Problem
When using rlogin or telnet to log on to a machine running SCO UNIX System V/386 Release 3.2, the error message "bad login user id" is displayed.
SCO UNIX has C2 like security. This error message is caused
when login calls setluid(). The problem is that the loginid
has already been set because someone (root) did a "tcp stop"
followed by a "tcp start." When root logs in, a loginid is
automatically set. This loginid is passed on to inetd which
passes it on to rlogind or telnetd. rlogind or telnetd exec
/bin/login which inherits the previously set loginid. Then
login calls setluid() which fails because the loginid is
already set. Solution
This error is caused by doing a "tcp stop" followed by a
"tcp start." init(M) has the unique property in that it does
not have a loginid associated with it. Therefore, when SCO
TCP/IP is started by init, there is no loginid associated
with the inetd process.This problem occures on systems running improved or C2 security, systems running traditional and low security will not have this problem.
The proper method to restart SCO TCP/IP follows: (This will work for all SCO TCP/IP versions and for all SCO Open Desktop / Open Server versions)
# init 1(while logged in as root on /dev/tty01)< here all the user processes are killed by "init 1" >
Then type CONTROL-d to proceed with normal startup.
NOTE: An alternate way to accomplish stopping and restarting TCP/IP 1.1, 1.2.0 and 1.2.1 and SCO Open Desktop 2.0 is described in another script in this database entitled:
"How to stop and start SCO TCP/IP without bringing the system
down" - - it tcpip #122.NOTE: This following method will work only for SCO Open Desktop 3.0 (The above mentioned fix is already included in SCO ODT 3.0)
NFS must be stopped before TCP/IP can be stopped.
# nfs stop# tcp stopInit a will start up TCP/IP after which NFS can be restarted.
# init a# nfs start See also
init(M), setluid(S)