On Tue, May 24, 2005 at 12:18:50PM +0100, Chris Green wrote:
I know quite a few daemons/servers are no longer started up by inetd, is there any logic to whether they are started this way or not?
Well, the theory goes that if you have a service that isn't used very often then you will start it from inetd, as it saves the program from sitting in the background doing nothing apart from eating Ram. Of course if you have to start the program each time someone accesses it then the performance may not be so great. Basically a tradeoff between how quickly something starts to how many resources they are using.
Further to this (and more importantly) how does one work out how an IP service is started if it's not in inetd.conf?
It will (usually) be started by init, take a look in /etc/init.d/ for the startup scripts, and /etc/rc*.d for the links that start (and stop!) them according to the runlevel of the machine. (I'd google for more info on init and the boot process, how init starts services etc if you need it as it will be explained better than I can do here.)
Adam