[cobalt-security] RE: /etc/inetd.conf

["Dean Hall" <dean@xxxxxxxxx>]

>
> Sorted the problem it was named in /etc/locked along with monitor. Is this
> good news or bad news (why would it be there?)
> Thanks again
> Paul

Inetd is started at boot time.  Looking at the startup script
/etc/rc.d/init.d/inet shows that a lock file is created.  On my RaQ4 the
lock file is /var/lock/subsys/inet.  I don't believe you mentioned the type
of Cobalt system you are using.

Looking at the script some more shows that when inet is stopped by normal
means, the lock file is removed.

The purpose of the lock file is to prevent more than one instance of inetd
(or monitor, or whatever) from running at the same time.  If your inetd
died an unnatural death, the lock file would remain and prevent restart.

Did you perhaps change the inetd.conf and then kill inetd with the intention
of restarting it and having it reread the configuration file?  This is not
the correct procedure for inetd.  The man page tells how to get the config
reread.