-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Commands With No Output Always Timeout #11
Comments
Hello, Yes, this is related with the previous issue. As we do not handle the return code of the process we cannot see if it finish if it does not return anything. That happens in your case because you are launching a command to a remote server. I will see if I can do something similar to what I did in issue #8. I guess I could create a temp script for each command and append a return string to this script. In that case I will be able to guarantee that there is always an output. |
A good test command for this is: Invoke-Command -ComputerName serverName {(Get-Service serviceName).WaitForStatus('Running','02:00:00')} Thx very much. These classes are quite useful. |
Hi, If you use the v1.7 you should have no problem. You only have to enable the remote mode.
Best regards |
Is there any situation where you wouldn't want to use remote mode? |
If you run a command that does not return any output we will sit and poll expecting an output till we hit the timeout.
The text was updated successfully, but these errors were encountered: