Automize unix commands how to#

Ping is one of the most basic networking troubleshooting commands. The 0.01 fifteen minute numbers tells you we're seeing something waiting only one time in a hundred. The 0.10 one minute load basically tells you that every 10th time the system checks, there is one process having to wait for acess to the CPU. In this case, the system isn't breaking a sweat. The uptime command shows you this along with the load averages that indicate how hard this system is working to keep up with the load. These numbers may seem huge but the system was been running for roughly a year.

Notice the RX (receive) and TX (transmit) packets counts as well as the same basic statistics shown in bytes. You might have a 'bonded' interface (like the one shown above) in which case, multiple physical interfaces are combined to provide more throughput. TX packets:946779445 errors:0 dropped:0 overruns:0 carrier:0 UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1

bond0 Link encap:Ethernet HWaddr 78:2B:CB:44:BF:DA These days, you may see both ipv4 and ipv6 addresses. It will tell you about your network interfaces, the state that they're in, your assigned IP address(es), and even provide some counts of packets that have crossed the interface since the system was last booted. One of the most basic networking commands is ifconfig. Let's run through the most useful networking commands that you'll find on Unix systems and maybe suggest some options you maybe never tried.

Automize unix commands how to#

Working on the command line was always a thrill, but understanding how Unix systems work together and how to do basic network troubleshooting brought the work to a new high. Working on Unix systems was never the same after that.