Inetd vs Rc.D

Suppose that I want to run SSH Daemon, what is the benefit of having the daemon integrated within Inetd Daemon??? Or is it better to have the daemon available under rc.d initialization script?

Another way .. why someone prefer to put SSHD into inetd where another people prefer to put in RC.D Script?
Who is Participating?
    -i      Specifies that sshd is being run from inetd(8).  sshd is normally
             not run from inetd because it needs to generate the server key
             before it can respond to the client, and this may take tens of
             seconds.  Clients would have to wait too long if the key was
             regenerated every time.  However, with small key sizes (e.g.,
             512) using sshd from inetd may be feasible.
Inetd is easier to manage since you can update the binary without shutting down the main daemon, but there is a minor performance penalty. Whether the performance penalty is an issue in your environment is something you'll have to test. Also most pre-packaged installation packages use the rc.d method.
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

shd running from inetd takes more system resources and therefore has less performance.
Well, it's true if there is rather high ssh traffic(at least one session at time).
If You use ssh for Yourself only, and logging in once a day - the inetd way would take less resources ;)

Is it homework? Does not look like in fact.
inetd is uncontrollable.
> inetd is uncontrollable.
What You mean by that?
One can use firewall, tcpwrappers, set max concurrent services. And for successors of inetd like xinetd much more...
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.