How complex of a daemon should be run through inetd?
Posted
by amphetamachine
on Server Fault
See other posts from Server Fault
or by amphetamachine
Published on 2010-05-28T17:58:50Z
Indexed on
2010/05/28
18:02 UTC
Read the original article
Hit count: 368
What is the general rule for which daemons should be started up through inetd? Currently, on my server, sshd, apache and sendmail are set up to run all the time, where simple *NIX services are set up to be started by inetd.
I'm the only one who uses ssh on my computer, and break-in attempts aren't a problem because I have it running on a non-standard port, and my HTTP server gets maybe 5 hits a day that aren't GoogleBot.
My question is, what are the benefits vs. the performance hits associated with running a complex daemon like sshd or apache through superserver, and what, if any successes or failures have you had running your own daemons in this manner?
© Server Fault or respective owner