Ps Command - Oracle Fujitsu SPARC M12-1 Service Manual

Table C-5 ping Command Options
Operand/Option
hostname
-g hostname
-i interface
-n
-s
-svR
The following example shows the output from the ping command.
# ping -s 10.24.187.50
PING 10.24.187.50: 56 data bytes
64 bytes from 10.24.187.50: icmp_seq=0. time=0.555 ms
64 bytes from 10.24.187.50: icmp_seq=1. time=0.400 ms
64 bytes from 10.24.187.50: icmp_seq=2. time=0.447 ms
^C
----10.24.187.50 PING Statistics----
3 packets transmitted, 3 packets received, 0% packet loss
round-trip (ms)
#
C.6

ps Command

The ps command displays a list of process statuses. When no options are specified,
the command outputs information on those processes that have the same execution
user ID as the user executing the command and the same control terminal.
If you specify an option, output information is controlled by the option.
Table C-6
troubleshooting.
Description
When you send a probe packet to
hostname, a message is returned.
Forces the probe packet to go
through the specified gateway.
Specifies the interface to be used for
sending and receiving a probe
packet.
Converts a host name into an IP
address and displays it.
ping is repeated at an interval of 1
second.
Pressing the [Ctrl] + [C] keys stops
ping, and then displays the statistics.
Displays the routes that probe
packets have passed through at an
interval of 1 second.
min/avg/max/stddev = 0.400/0.467/0.555/0.079
lists the options of the ps command and how these options are useful for
Application
Allows you to confirm that a host is
active on the network.
Allows you to test the quality of
individual routes by sending
packets to the target host via the
various specified routes.
Allows you to easily check the
secondary network interface.
Allows you to check the IP address
instead of the host name.
Allows you to check intermittent or
long-term network events. You can
view nighttime network events at a
glance by piping the ping output to
a file.
Displays the routes and hop counts
of probe packets, allowing you to
compare multiple routes to identify
any bottleneck.
Appendix C Oracle Solaris Troubleshooting Commands 217