Enabling Telnet in Runlevel 1
 

hello Friends ,
I am new to Linux Kernel and struck in a problem ....


I am booting my cliet from server in Runlevel 1. to perform Remote Restore.


I have been asked to activate Telnet Session in Runlevel 1 which after reveiwing few documents I found that networ drivers are not loaded in RunLevel & so it is not possible to start Telnet Session.

But from client to Server by loading the exe /usr/bin/telnet and its shared library I am able to make telnet connection.

If I try from server to Client it shows unable to connect: connection refused.

SO I tried to boot the client in Runlevel 3 so that network interfaces are available. but the systemhands after showing message

INIT: No more processes left.

Is this the right solution to enable telnet.


Please Guide me further

Thank You in advance

Aditya Singh Tomar

Yes, you need to have networking running to enable telnet.
You don't need to explicitly change runlevel, will do it (you may need to change the /etc/rc.d bit; I think Red Hat used to use /etc/rc.d/init.d/ when I used it years ago).

The message means that it has shut down all the user processes in the particular runlevel; it normally does this when you change runlevels (especially to shutdown or reboot). You should expect the system to start up runlevel 3, enabling networking and firewalls and then bring up system logins again.

The message can be caused by telnetd or inetd (configured for telnet) not running, depending on which you are using. It can also be caused by the network being down, or the telnet port being blocked by a firewall.

Thanks for your message.



1. I have a confusion ! Is it possible to start network devices while being in Runlevel 1 by the
/etc/rc.d/init.d/networking start

2. How to enable inetd server/xinetd server in runlevel 1

as I am asked to be in runlevel 1 and start Telnet Service.


Aditya

Runlevel 1 typically means 'no networking' so really you shouldn't be trying to get telnet up in runlevel 1. If you really need to not be in runlevel 3 then I'd suggest maybe editing inittab and setting up a runlevel 2 that is runlevel 1 with networking, although that's about all runlevel 3 is anyhow. If you change runlevel 1 to have it start networking (to be able to telnet) then it's not really runlevel 1 anymore, and if you had bad enough networking problems you wouldn't be able to use runlevel 1 to fix them.

Don't run telnet at all.
 

Slightly offtopic, but still good nonetheless..

Just some advice: these days, you shouldn't be running a telnet server at all. Sending out a password plaintext over a network is a bad idea.

If anything, run a SSH server. It's much more secure.