Mandriva This Forum is for the discussion of Mandriva (Mandrake) Linux. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
01-25-2005, 02:16 AM
|
#1
|
Member
Registered: Jan 2005
Location: chennai
Distribution: mandrake
Posts: 70
Rep:
|
rlogin command not found...
i am using mandrake linux for 5 computers.i need to handle the other systems by a single system.
when i gave #rlogin 10.255.230.123
rlogin command not found.
when i have to poweroff other systems by this system,how can i do that?
|
|
|
01-25-2005, 02:32 AM
|
#2
|
Member
Registered: Jan 2005
Location: Övik, Sweden
Distribution: MDK 10.1
Posts: 450
Rep:
|
Do not use rlogin (not even at gunpoint). It has been deprecated a loong time along with telnet.
ssh is the secure replacement for the above (with scp for secure copy).
Install openssh-server on the remote machines and openssh-clients on your local one and you should be good to go.
Another alternative is to install webmin on the remotes. That way you can admin them through a browser.
- Peder
|
|
|
01-25-2005, 02:39 AM
|
#3
|
Member
Registered: Jan 2005
Location: France / Bretagne
Distribution: Debian / Gentoo
Posts: 71
Rep:
|
when u have installed open ssh ,
start the deamon sshd
after with another machine
connect , and
|
|
|
01-25-2005, 02:55 AM
|
#4
|
Member
Registered: Jan 2005
Location: chennai
Distribution: mandrake
Posts: 70
Original Poster
Rep:
|
sir connect to system by,
#ssh 10.255.240.137
and log on to the system and i started sshd.
when i give shutdown -h now it said...
[root@Simlab-node10 Desktop]# shutdown -h now
Broadcast message from root (pts/0) (Tue Jan 25 14:28:48 2005):
The system is going down for system halt NOW!
[root@Simlab-node10 Desktop]#
after that nothing happens....the system not shutdown....pls help me....
|
|
|
01-25-2005, 03:06 AM
|
#5
|
Member
Registered: Jan 2005
Location: chennai
Distribution: mandrake
Posts: 70
Original Poster
Rep:
|
[root@Simlab-node3 staff]# ssh 10.255.240.157
ssh: connect to host 10.255.240.157 port 22: Connection refused
the address is correct but not connecting help me....
|
|
|
01-25-2005, 03:13 AM
|
#6
|
Member
Registered: Jan 2005
Location: Övik, Sweden
Distribution: MDK 10.1
Posts: 450
Rep:
|
Instead of 'shutdown -h now' you could just enter 'halt' or 'reboot' (depending on what you want).
And if it doesn't shutdown, what happens? Does it hang somewhere?
Regarding "Connection refused"; have you started sshd on that server? Do a 'service sshd restart' and 'chkconfig sshd on'
If it's running, make sure you don't have any firewall rules preventing access to port 22 from your client.
Also check if there's any entry in /etc/hosts.deny preventing access.
- Peder
|
|
|
01-25-2005, 03:19 AM
|
#7
|
Member
Registered: Jan 2005
Location: chennai
Distribution: mandrake
Posts: 70
Original Poster
Rep:
|
root@Simlab-node3 staff]# ssh 10.255.240.157
ssh: connect to host 10.255.240.157 port 22: Connection refused
[root@Simlab-node3 staff]# servise sshd restart
bash: servise: command not found
[root@Simlab-node3 staff]# service sshd restart
Stopping sshd: [ OK ]
Starting sshd: [ OK ]
[root@Simlab-node3 staff]# ssh 10.255.240.157
ssh: connect to host 10.255.240.157 port 22: Connection refused
[root@Simlab-node3 staff]# chkconfig sshd on
[root@Simlab-node3 staff]# chkconfig sshd on
[root@Simlab-node3 staff]# ssh 10.255.240.157
ssh: connect to host 10.255.240.157 port 22: Connection refused
[root@Simlab-node3 staff]
this is what happened .........
|
|
|
01-25-2005, 05:41 AM
|
#8
|
Member
Registered: Jan 2005
Location: Övik, Sweden
Distribution: MDK 10.1
Posts: 450
Rep:
|
No.
You have to run the 'service....' and 'chkconfig....' commands on the remote server, 10.255.240.157.
What you have done is started sshd on Simlab-node3 (nothing wrong with that but it won't help you connecting to 10.255.240.157).
- Peder
|
|
|
All times are GMT -5. The time now is 11:48 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|