I know I can do
Netsh ...; restart - which reboots the windows box fine.
So the ; kinda serves as && in bash, but chef seems to hang on to it and doesn't terminate the run.
It seems like as soon as the ip is changed, the chef-run holds on until it eventually times out.
I tried doing
Netsh; exit
Netsh; return
And it still didn't terminate the run.
The other option is to change the ip and only apply on a reboot, but i couldn't see you could do that with netsh or wmi.
I could change the ip in the registry but I think that's not a nice way of doing it.
Cheers,
Simon.
Sent from my iPhone
Disclaimer This message is intended only for the use of the person(s) ("Intended Recipient") to whom it is addressed. It may contain information which is privileged and confidential. Accordingly any dissemination, distribution, copying or other use of this message or any of its content by any person other than the Intended Recipient may constitute a breach of civil or criminal law and is strictly prohibited. If you are not the Intended Recipient, please contact the sender as soon as possible. Totaljobs Group Limited Registered Office: Holden House, 57 Rathbone Place, London, W1T 1JU, UK Registered in England and Wales under company no. 4269861 |
Archive powered by MHonArc 2.6.16.