Monitoring inetd

[Roberto Volsa]

The objective is create a package which monitors inetd; but inetd is a socket and it only listen: a process born only if a remote request reach the server. Thus: which processes have i to monitor and write down on the configuration files of the package?

[Alan Riggs]

inetd will log contact requests, etc. to the files specified in etc/inetd.conf

[James R. Ferguson]

Hi:

I'm not sure exactly what you want. the inetd daemon will be visible to 'ps' if you want to make sure its running.

You can start inetd with connection logging enabled. The default is not to do so. See "man inetd" for more information. Hopefully this information helps you.

...JRF...

[Roberto Volsa]

the problem is what i have to write in the SERVICE_CMD! Qhat command does start inetd? I don't think i can put init in SERVICE_CMD raw!

[Alan Riggs]

Do I understand that you want a serviceguard package to swap inetd back and forth between primary and failover hosts?

Why?

Inetd should run independently on each box. It is necessary for basic networking functionality.

[Kofi ARTHIABAH]

inetd is started at startup (run level 2 and higher) by the script /sbin/rc2.d/S500inetd with the start parameter.

You can configure your setup so that if inetd dies - it gets restarted:

INETDRUNNING=`ps -ef | grep -c [i]netd`
if [ ! $INETDRUNNING ]
then
/sbin/rc2.d/S500inetd start
fi


Good luck

[James R. Ferguson · Accepted solution]

Hi:

As Alan asked, are you talking about MC/ServiceGuard 'packages'? If so, I agree with him, inetd is not something that you want to start/stop/reconfigure in a failover. A similar thread on this issue can be found here:

http://my1.itrc.hp.com/cm/QuestionAnswer/1,1150,0x726168c57f64d4118fee0090279cd0f9,00.html

Does this help?

...JRF...

[Roberto Volsa]

Yes, the package has to monitor inetd process; the package is used for load balancing purposes and each package with different ips let the customer know where messages aresent.
Roberto