Re: daemon/initd
Correcting my mistakes...
On Wed, Sep 22, 1999 at 04:31:28PM +0930, John Pearson wrote
> On Wed, Sep 22, 1999 at 03:13:12PM +1300, zdrysdal@diagnostic.co.nz wrote
> > Hi
> >
> > Can someone properly explain to me the differences between how a process
> > starts up as a daemon as apposed to a process which starts up via initd as
> > i am a little unsure.
> >
> > thanx
> >
>
> Assuming that by 'initd' you mean 'inetd', not a whole lot.
>
> Inetd is used only with daemons that normally listen on a
> network port, usually so they can offer some service (e.g.,
> telnetd). Not all daemons do this (e.g., apmd), and these
> daemons don't get run from inetd.
>
> Inetd provides some basic functionality required of any network
> service, and that otherwise is provided by the daemon:
> - Listening for connections;
> - Establishing connections;
> - Spawning a child process to handle the connection.
>
> The advantages to using inetd lie in the fact that you can
> have a single process listening for connections on many
> services, saving resources, and in the fact that it allows
> you to centralise access controls for network services:
> Inetd is linked against the tcpwrappers library, which
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"Inetd is commonly used with tcpd and may be linked against
tcpwrappers", would be closer to the truth.
> allows you to control access to services based on service
> name or port number, client IP and so on using
> /etc/hosts.deny and /etc/hosts.allow (man 5 hosts_access).
>
>[snip]
John P.
--
huiac@camtech.net.au
john@huiac.apana.org.au
"Oh - I - you know - my job is to fear everything." - Bill Gates in Denmark
Reply to: