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?
Further to this (and more importantly) how does one work out how an IP service is started if it's not in inetd.conf?
In particular I can't see what starts the IMAP4 services but they most definitely do start. There's an 'imap2' entry in inetd.conf but not an 'imap4' one, is this the one that starts an connection on port 143?
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?
Further to this (and more importantly) how does one work out how an IP service is started if it's not in inetd.conf?
In particular I can't see what starts the IMAP4 services but they most definitely do start. There's an 'imap2' entry in inetd.conf but not an 'imap4' one, is this the one that starts an connection on port 143?
Chris, I'm using cyrus imap from CMU - it's is not longer supported by inetd. It is started (on SuSE 9.2) in /etc/init.d, where there is a script named cyrus. This is sym linked to start and kill scripts in the relevant runlevel subdirectories (rc5.d etc).
Stuart.
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
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.
-
Adam Bower -
Chris Green -
Richard Kettlewell -
Stuart Bailey