Question about enabling ssh on ESXi 4.0

[maxiscaleit]

When enabling ssh on ESXi 4.0, will issuing the 'services.sh restart' command after editing inetd.conf interrupt any currently running VMs, or does the process serving the VM run as a completely separate process and won't be affected when I run that shell command?

[DSTAVERT]

No. You need to do

ps | grep inetd

it will display the PID that inetd is using

then

kill -HUP PID (the pid number from the ps results)

[Troy_Clavell]

no, restarting the management agents should have no impact on your guests.

....but it won't hurt to disable any startup/shutdown options you have configured for your guest.

[DSTAVERT]

I should have made it clearer. The services.sh restart does not restart inetd.

[maxiscaleit]

So just for confirmation do I need to do a 'services.sh restart' and THEN kill the inetd ps, or will running a 'kill -HUD <inetd ps>, automatically kill and restart inetd without the need for running the shell script

[DSTAVERT]

Only the kill. services.sh restart only restarts the management agents not inetd . I have found that after enabling ssh that I need to do a services.sh restart perhaps more frequently.