AIX

Yes, each O/S may have nicities in how you properly remove services from listening. Usually, you deconfigure inetd but leave the services registered, in case a client wants to know the port to connect on another host.

If you done edit /etc/inetd.conf

you must restart the service.

Code:

#stopsrc -s inetd
#startsrc -s inetd

or refresh -s inetd

best regard

Yes, generally inetd and other classic daemons will reread config if you send it the right signal with a kill, sighup I think, and the refresh thing maybe a wrapper for that.

As it is, things are a little bit more complicated in AIX: most of the system services are managed by a AUX-specific piece of software called the "System Resource Controller" (SRC). It supports signal communication too (so you are partly correct), but that is not the only function.

Most services ("inetd" included) are started with "startsrc", stopped with "stopsrc", etc.. All these "*src" commands are using the SRC frontend to control service processes controlled by the SRC. Here are the most important commands:

For further information here is the link to IBMs documentation about the SRC.

I hope this helps.

bakunin

Yes, any daemon running under a master like src in AIX has to be managed by that master. The src ensures it is restarted if it fails, but generally a well written daemon like inetd does not.

Since we have delved so deeply into SRC the missing commands are:

mkssys
chssys
and rmssys

The mkssys command adds a new subsystem definition to the subsystem object class. The chssys command modifies an existing subsystem definition in the subsystem object class. The rmssys command removes an existing subsystem definition from the subsystem object class.

In short, you can add/modify/remove daemons to the SRC system.