Chris Green chris@areti.co.uk writes:
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?
Starting from inetd is only useful if a separate process is used to service every connection. BIND is a widely used counterexample - it uses a single process to serve all requests.
A less widespread counterexample is my software jukebox, which again serves all requests through a single process, but even if it didn't then inetd would not be useful as the server needs to keep running to pick new tracks to play.
Further to this (and more importantly) how does one work out how an IP service is started if it's not in inetd.conf?
Use netstat or lsof to discover what process is listening on the relevant socket and grep /etc/init.d/* for its name.