- Goals
- User guide
- History
- Application testing list
- Getting Started
- Hardware Compatibility List
- Hardware requirements
- JNode Commands
- acpi
- alias
- arp
- basename
- beep
- bindkeys
- bootp
- bsh
- bzip2
- cat
- cd
- class
- classpath
- clear
- compile
- console
- cpuid
- date
- del
- device
- df
- dhcp
- dir
- dirname
- disasm
- echo
- edit
- eject
- env
- exit
- gc
- grep
- gzip
- halt
- help
- hexdump
- history
- ifconfig
- java
- kdb
- leed, levi
- loadkeys
- locale
- log4j
- ls
- lsirq
- man
- memory
- mkdir
- mount
- namespace
- netstat
- onheap
- page
- ping
- plugin
- propset
- pwd
- ramdisk
- reboot
- remoteout
- resolver
- route
- rpcinfo
- run
- startawt
- syntax
- tar
- tcpinout
- thread
- time
- touch
- unzip
- utest
- vminfo
- wc
- zip
- JNode GUI
- JNode Shell
- Performance
- Status
- Classlib developers guide
- Developer guide
- Tester guide
- Porting guide
- Blogs
- Project development
- Glossary
- Proposals
- FAQ
- Papers & presentations
- References
- Research
ping
ping
| Synopsis | ||
| ping | <host> | Ping a remote host |
|
Details | ||
| The ping command sends ICMP PING messages to the remote host given by <host> and prints statistics on the replies received. Pinging is a commonly used technique for testing that a remote host is contactable. However, ping "failure" does not necessarily mean that the machine is uncontactable. Gateways and even hosts are often configured to silently block or ignore PING messages. | ||
|
Bugs | ||
| The ping command uses hard-wired parameters for the PING packet's TTL, size, count, interval and timeout. These should be command line options. | ||
