05-21-2008
# Shell, login, exec, comsat and talk are BSD protocols.
#
shell stream tcp nowait root /usr/sbin/in.rshd in.rshd
shell stream tcp6 nowait root /usr/sbin/in.rshd in.rshd
login stream tcp6 nowait root /usr/sbin/in.rlogind in.rlogind
I have seen this in my /etc/inetd.conf.
9 More Discussions You Might Find Interesting
1. Solaris
Hi all,
This is the first time i am using this forum to clear my doubt.
I am using Sun solaris 9 Operating System, I am stuck up with a problem regarding webmin server.I logged in to webmin as system administrator (root)and then clicked change passwords module. It shows the list of... (1 Reply)
Discussion started by: Kundu
1 Replies
2. Solaris
Hello Guys,
I have just joined this forum & hope that I will find a solution to my question.
I have configured NFS shares on my machine solaris 10 (5.10). Shares have rw access for everyone.
Tried starting NFS server daemon with following command.
svcadm -v enable -t network/nfs/server... (3 Replies)
Discussion started by: say_hi_ravi
3 Replies
3. Tips and Tutorials
The most common Solaris exit codes you will see is 2 or 8, but have you ever had a different exit code and wondered what it means ?
Well you need not wonder no more...
Patch Exit Codes
----------------
0 No error
1 Usage error
2 Attempt to apply a patch that's already... (1 Reply)
Discussion started by: Tornado
1 Replies
4. Solaris
Hi,
Occasionally I am getting the port state in CLOSE_WAIT for long time in the solaris server. I am not sure is it application problem or not. Because we are using port 9009 for Tomcat process in our web application, some time when I start the application, the port 9009 is in CLOSE_WAIT... (2 Replies)
Discussion started by: mgmk.84
2 Replies
5. Solaris
Hi,
While we rebooting solaris server ,the system going to Maintenance mode instead of login console.
even we are not able to run fsck command . Thanks in advanced for help.
log attached FYI
Executing last command: boot
Boot device: /pci@83,4000/FJSV,ulsa@2,1/disk@0,0 File and args:... (3 Replies)
Discussion started by: helplineinc
3 Replies
6. Solaris
Hi everyone,
I am new here and I just want to ask for the expert advice from you guys about the problem/issue I am encountering with network printer defined on a Solaris 10 machine.
I have this printer named 'printerA' which I already added via printmgr utility. As an output, here is the... (4 Replies)
Discussion started by: triptrops
4 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I am currently in the process of implementing port based authentication(802.1x) in my home network through radius(FreeRadius).
I want all my clients to use a certificate for authenticating (eap-tls)
However openssl's massive amount of configuration options has me a bit confused.
And... (0 Replies)
Discussion started by: regexp
0 Replies
8. Shell Programming and Scripting
Good day all.
I'm trying to rename some files in my home directory with some bizarre results. Basically I need to change the IP address in the filename to the hostname which I ggrep from within the file:
-rw-r--r-- 1 bh694n nrc 5095 May 2 20:03 alarms_999.189.161.146.log... (2 Replies)
Discussion started by: BRH
2 Replies
9. Solaris
Hi,
On my Sun Ultra 45, display was flickering. After changing PCI slot of graphic card (XVR-300), display stablized, but, now X-server not starting. I am getting following messages
The X-server can not be started on display : 0...
See file/var/dt/Xerrors for details.
the output of... (8 Replies)
Discussion started by: rakhsin
8 Replies
LEARN ABOUT MINIX
rlogind
RLOGIND(8) System Manager's Manual RLOGIND(8)
NAME
rlogind, in.rld - remote login server
SYNOPSIS
login stream tcp nowait root /usr/sbin/in.rld in.rld
tcpd login /usr/sbin/in.rld
DESCRIPTION
Rlogind is the server for the rlogin(1) program. The server provides a remote login facility with authentication based on privileged port
numbers from trusted hosts.
Rlogind listens for service requests at the port indicated in the ``login'' service specification; see services(5). When a service request
is received the following protocol is initiated:
1) The server checks the client's source port. If the port is not in the range 0-1023, the server aborts the connection.
2) The server checks the client's source address and requests the corresponding host name (see gethostbyaddr(3), hosts(5) and
named(8)). If the hostname cannot be determined, the dot-notation representation of the host address is used.
Once the source port and address have been checked, rlogind allocates a pseudo terminal (see tty(4)), and manipulates file descriptors so
that the slave half of the pseudo terminal becomes the stdin , stdout , and stderr for a login process. The login process is an instance
of the login(1) program, invoked with the -r option. The login process then proceeds with the authentication process as described in
rshd(8), but if automatic authentication fails, it reprompts the user to login as one finds on a standard terminal line.
The parent of the login process manipulates the master side of the pseduo terminal, operating as an intermediary between the login process
and the client instance of the rlogin program. In normal operation, the packet protocol described in tty(4) is invoked to provide ^S/^Q
type facilities and propagate interrupt signals to the remote programs. The login process propagates the client terminal's baud rate and
terminal type, as found in the environment variable, ``TERM''; see environ(7). The screen or window size of the terminal is requested from
the client, and window size changes from the client are propagated to the pseudo terminal.
SEE ALSO
rlogin(1).
DIAGNOSTICS
All diagnostic messages are returned on the connection associated with the stderr, after which any network connections are closed. An
error is indicated by a leading byte with a value of 1.
``Try again.''
A fork by the server failed.
``/bin/sh: ...''
The user's login shell could not be started.
BUGS
The authentication procedure used here assumes the integrity of each client machine and the connecting medium. This is insecure, but is
useful in an ``open'' environment.
A facility to allow all data exchanges to be encrypted should be present.
A more extensible protocol should be used.
4.2 Berkeley Distribution May 24, 1986 RLOGIND(8)