Comments (4)
Thinking about picking this up (kind of low on time for other issues), some questions beforehand:
n
means total successful + unsuccessful probes, or only one of those?- How should it interact with the
-r
flag? - Due to how recently durations were refactored, output may be incorrect sometimes. Is that ok for now or let's wait for fixes?
from tcping.
Hey Alex,
Thanks for being such a helping hand 🤝
for questions 1 and 2, it means probe/ping a destination n
times regardless of the result. similar to the -c
flag of the ping
utility itself. So if we say tcping example.com 443 -c 1
, we want to exit the program after one probe, whether successful or not.
- Due to how recently durations were refactored, output may be incorrect sometimes. Is that ok for now or let's wait for fixes?
That is fine. However, there won't be a release until we address #83
from tcping.
So for -c 3 -r 2
should ping 2 times, try to resolve, ping 1 time and quit, right?
from tcping.
So for
-c 3 -r 2
should ping 2 times, try to resolve, ping 1 time and quit, right?
yes. Although in reality, it does not make much sense to specify -r 2
when probing thrice but I get your point.
Think of this option as doing a quick check to a destination and exiting instead of using nc -w 1
or tcping and then quickly ctrl+c
.
from tcping.
Related Issues (20)
- README Translation - Chinese
- add TTL in output please HOT 3
- Please add "count" and "interval" option HOT 3
- Add tcping to winget
- output interface HOT 13
- v2.0.0 is not listed on Go module proxy due to missing /v2 suffix in the "module" path HOT 8
- fix database user input flag HOT 8
- Database closure before the appropriate time. HOT 2
- Include db.go in the Makefile HOT 10
- Use standard `time.Duration` for storing/working with durations HOT 3
- Automate the release process
- Starting and exiting immediately prints "NaN% packet loss" HOT 1
- Windows terminal link in `README.md` is broken
- Time report is not accurate HOT 4
- Move any output-related logic to printers (and vice-versa) HOT 2
- `-c` flag does not print `TCPing ended at` information HOT 2
- One failed probe prints `No response received for 0 seconds` HOT 4
- Add BSD support
- fix CI warnings HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from tcping.