Skip to content
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

paping does not set %ERRORLEVEL% #5

Closed
GoogleCodeExporter opened this issue Apr 20, 2015 · 3 comments
Closed

paping does not set %ERRORLEVEL% #5

GoogleCodeExporter opened this issue Apr 20, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Download paping.
2. Create a batch file that runs paping and checks %ERRORLEVEL% environnment 
variable.
3. Run the batch file and see that %ERRORLEVEL% is always 0, no matter if the 
ping wast successful or not.

What is the expected output? What do you see instead?
I expected paping to set %ERRORLEVEL% in the same manner ping.exe does (0 if 
ping successful, 1 if "request timed out or other error).

What version of the product are you using? On what operating system?
paping 1.5.1 x86, Windows 7 Professional

Please provide any additional information below.

Batch file example:

paping google.com -p 80 -c 4
goto %ERRORLEVEL%
:0
@echo Ping successful!
goto:eof
:1
@echo Ping error!
goto:eof

Original issue reported on code.google.com by CitizenO...@gmail.com on 10 Mar 2011 at 5:58

@GoogleCodeExporter
Copy link
Author

Original comment by pap...@lists.gotinker.com on 21 Apr 2011 at 7:46

  • Changed state: Started

@GoogleCodeExporter
Copy link
Author

Original comment by pap...@lists.gotinker.com on 21 Apr 2011 at 9:03

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

A return code of '1' is now returned if any problem occurs connecting to a host 
one or more times

Original comment by pap...@lists.gotinker.com on 21 Apr 2011 at 9:11

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant