SEO

In HP-UX (from what I can see) it is possible to start daemons as
startup either:
(a) by creating a file in /sbin/init.d and linking it to one of the
rc.x directories as a Sxxx file or,
(b) creating an entry for the daemon in /etc/inetd.conf

I'm aware there are a number of options you can use to configure the
operation of the daemon in /etc/inetd.conf. It does not appear that
these options are availalbe/needed/appropriate for daemons started
using /sbin/init.d ??? Can someone provide me with guidance or point
me towards a good source of reference ?

One of those questions I should have asked a long time ago !

"championsleeper" <strepxe@yahoo.co.uk> schreef in bericht
news:103a78f3.0310281537.d7bbceb@posting.google.co m...
> In HP-UX (from what I can see) it is possible to start daemons as
> startup either:
> (a) by creating a file in /sbin/init.d and linking it to one of the
> rc.x directories as a Sxxx file or,
> (b) creating an entry for the daemon in /etc/inetd.conf
>
> I'm aware there are a number of options you can use to configure the
> operation of the daemon in /etc/inetd.conf. It does not appear that
> these options are availalbe/needed/appropriate for daemons started
> using /sbin/init.d ??? Can someone provide me with guidance or point
> me towards a good source of reference ?
>
> One of those questions I should have asked a long time ago !

Champonsleeper,


There is a big difference between the two approaches.

a) Is for standalone daemons or programs that have to run ones when changing
runlevels.
b) Is for daemons that have to be activated by "net users" for there use of
your server.

Like the telnet daemon, it sleeps until a net user wants to connect by
telnet. The inetd daemon starts a telnet daemon to make the connection for
this net user.

Important differences between option a) and b).

Option a) will start one daemon at runlevel activation

Option b) will start a daemon for each net user request as long as inetd is
active. So you can multiple instances of the same daemon.


Regards,


Jan Gerrit Kootstra

"Jan Gerrit Kootstra" <jan.gerrit@kootstra.org.uk> wrote in message news:<3f9f5b03$0$79342$5fc3050@dreader2.news.tisca li.nl>...
> "championsleeper" <strepxe@yahoo.co.uk> schreef in bericht
> news:103a78f3.0310281537.d7bbceb@posting.google.co m...
> > In HP-UX (from what I can see) it is possible to start daemons as
> > startup either:
> > (a) by creating a file in /sbin/init.d and linking it to one of the
> > rc.x directories as a Sxxx file or,
> > (b) creating an entry for the daemon in /etc/inetd.conf
> >
> > I'm aware there are a number of options you can use to configure the
> > operation of the daemon in /etc/inetd.conf. It does not appear that
> > these options are availalbe/needed/appropriate for daemons started
> > using /sbin/init.d ??? Can someone provide me with guidance or point
> > me towards a good source of reference ?
> >
> > One of those questions I should have asked a long time ago !
>
> Champonsleeper,
>
>
> There is a big difference between the two approaches.
>
> a) Is for standalone daemons or programs that have to run ones when changing
> runlevels.
> b) Is for daemons that have to be activated by "net users" for there use of
> your server.
>
> Like the telnet daemon, it sleeps until a net user wants to connect by
> telnet. The inetd daemon starts a telnet daemon to make the connection for
> this net user.
>
> Important differences between option a) and b).
>
> Option a) will start one daemon at runlevel activation
>
> Option b) will start a daemon for each net user request as long as inetd is
> active. So you can multiple instances of the same daemon.
>
>
> Regards,
>
>
> Jan Gerrit Kootstra

Thankyou very much for the response. It is much clearer to me know and
explains why our application documents the startup of its consituent
components in different ways.

Cheers!

From this [and another reply] it appears that there are three methods
to to start daemons:

(a) by creating a file in /sbin/init.d and linking it to one of the
rc.x directories as a Sxxx file,
(b) creating an entry for the daemon in /etc/inetd.conf or
(c) starting it by listing it in /etc/inittab


Method (a) is for standalone daemons or programs that are intended to
run at specific runlevels. The method will start one daemon at
runlevel activation. The /sbin/init.d scripts are for starting
programs that may not use a network connection, such as accounting or
cron; or need to maintain a state between network connections, such as
ntp and ssh.

Method (b) is for daemons that have to be activated by network users
connecting to your server. This method will start a daemon for each
net user request as long as inetd is active. Consequently you can have
multiple instances of the same daemon. Many of what look like options
in inetd.conf are there to make sure that inetd itself opens the
network socket the same way that the daemon would if you started it
manually or out of /sbin/init.d. Inetd is really for starting services
that will only offer their service to a network connection. There are
a lot of these kinds of services with some intended for use by
multiple simultaneous clients. To manage this type of service
behaviour, the BSD people invented inetd as a way to minimize the
number of processes in a "wait for a network connection" state.

(c) This is the best place for daemons that need to be automatically
restarted if they happen to die. It's less common than /sbin/init.d
(which is itself started out by /etc/inittab).