[TAG] How to start (activate) rlogin and rsh?
thomas at edulinux.homeunix.org
Mon Sep 27 04:17:32 MSD 2004
On Mon, Sep 27, 2004 at 02:08:30AM +0200, Alex Kalman wrote:
I asked you last time NOT to top-post, and NOT to keep changing the subject
every time you reply and/or compose an e-mail that is continuing a thread. So
why do you continue to do it?
> I cannot start rsh. I continue to receive the message:
> 188.8.131.52: Permission denied.
> rsh: can't establish connection
You are really trying the wick here. You do not need rsh, you can accomplish
the same thing with ssh, if you'd only try. The program won't care, whether
you use rsh or ssh. Indeed, many packages/distros symlink rsh to the ssh
> 1. I have checked up a file /etc/inetd.conf:
> a) in.rshd -aL - it is activated (shell stream tcp nowait root
> /usr/sbin/tcpd in.rshd -L)- (look in an inetd.conf).
> b) in.rshd -L - it is activated (shell stream tcp nowait root
> /usr/sbin/tcpd in.rshd -aL)-(look in an inetd.conf).
This is on the machine that you're connecting _to_ (that acts as the server),
> 3. I cannot enter a computer in which is SUSE LINUX 7.3 by means of a
> command rlogin:
> a) I have checked up a file /etc/rc.config and has changed in line
> ("ROOT_LOGIN_REMOTE") "no" on "yes", but it has not helped.
It would do if you sourced the file afterwards:
by means of running the command: "YastConfig" as root. The environment needs
to know of the existence of the variable.
> There can be these files will help to find a mistake in definitions?!?
> We want to work only by means of commands rsh and rlogin. I am confident
> that it probably. If can that help us?!
You'd do well by checking /var/log/messages for any errors. But IMO, you're
wasting your time over a buggy protocol. Use ssh, it is much easier and more
securer. As I said before, the underlying program using it won't give a jot
[..snip rest of reply.. grrrrrr..]
-- Thomas Adam
$ source ~/.bash_history
More information about the TAG