Link to home
Start Free TrialLog in
Avatar of mickge
mickge

asked on

restarting inetd

I made a change to my /etc/inet/inetd.conf on a solaris 8 server and restarted inetd with the follwoing

/usr/bin/pkill -HUP inetd
and tried
/usr/bin/kill -HUP 178

this does not kill the process ?  Is there anohter way of restarting inetd

Thanks

Mick
Avatar of BobHB
BobHB

I  hardened a Solaris 8 box about 2 years ago and remember having the same problem.  I'll research my notes.

The best way would be to reboot the server; is that a possibility for you?
I believe the very best and absolutely the safest way to restart inedt is to restart the machine.  My notes say (quoting somebody) is that this way the "sanity" of the machine is ensured since the startup scripts have a certain order and dependencies.  The inetd.conf file is started in /etc/rc2.d/S72inetsvc and itself controls the starting of quite a number of services, services which you would have to stop (or kill) by yourself if you didn't reboot.
I believe the very best and absolutely the safest way to restart inedt is to restart the machine.  My notes say (quoting somebody) is that this way the "sanity" of the machine is ensured since the startup scripts have a certain order and dependencies.  The inetd.conf file is started in /etc/rc2.d/S72inetsvc and itself controls the starting of quite a number of services, services which you would have to stop (or kill) by yourself if you didn't reboot.
you can use:

/etc/init.d/inetsvc restart

or

/etc/init.d/inetd restart
RTFM - A SIGHUP doesn't stop inetd - it makes it reread its configuration file and makes it take place immediately.
ASKER CERTIFIED SOLUTION
Avatar of Tintin
Tintin

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of mickge

ASKER

My mistake here lads.  I thought that the process was killed and restarted.  So I was looking at the timestamp of the process - not knowing that it just re read the config file.

Also, really should of looked more carefully at the config as it blocks telnet inbound and I was trying to telnet outbound after giving it the HUP - which is why I didnt think my kill had worked