net start net stop and inetd

[Doug_3]

Our new sysadmin is using net stop and net start to recycle the inetd services. He will edit the inetd.conf file and change the ip on the nic's, then execute the stop/start commands to swap identical hp-ux boxes ip addresses.
Is this the correct way to do this? In the past we had reset the nic's and then forced the inetd to re-read the conf file or just re-boot. Are there other issues that are not being addressed with this technique?
I am concerned that other dependent services are not being reset correctly. Since we tried this we have had some serious performance issues with a report writer tool that uses odbc, ip and rpc to talk to the database server.
Thanks in advance,
Doug

[Steven E. Protter · Accepted solution]

If all you want to do is restart the inetd daemon:

inetd -c

Don't start/stop net

There are other components to the network that are not being reset properly and are probably causing the problems you report.

SEP

[Pete Randall]

Doug,

Being basically cowardly when it comes to changing things, I've always used the /sbin/set_parms command to set first the hostname, then the ip_address - then rebooted. I can't think of any drawbacks to net stop/start, I guess, but my cautious nature is going to stick to my tried and true method.


Pete

[Sridhar Bhaskarla]

Hi Doug,

No. /sbin/init.d/net stop and start will not affect inetd. If at all he wants to use /sbin scripts, he should be using /sbin/init.d/inetd. net start and stop can help to reconfigure the IPs and the default gateway.

I would run 'inetd -c' to re-read the configuration.

-Sri