gaspersic/the-art-of-command-line
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add sar link

Browse Source
This commit is contained in:
Fernando Almeida
2016-08-25 11:23:44 -03:00
parent 46011ec11c
commit 7e7991bf88
14 changed files with 28 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -317,7 +317,7 @@ mkdir empty && rsync -r --delete empty/ some-dir && rmdir some-dir
- Use `/proc`. It's amazingly helpful sometimes when debugging live problems. Examples: `/proc/cpuinfo`, `/proc/meminfo`, `/proc/cmdline`, `/proc/xxx/cwd`, `/proc/xxx/exe`, `/proc/xxx/fd/`, `/proc/xxx/smaps` (where `xxx` is the process id or pid).
- When debugging why something went wrong in the past, `sar` can be very helpful. It shows historic statistics on CPU, memory, network, etc.
- When debugging why something went wrong in the past, [`sar`](http://sebastien.godard.pagesperso-orange.fr/) can be very helpful. It shows historic statistics on CPU, memory, network, etc.
- For deeper systems and performance analyses, look at `stap` ([SystemTap](https://sourceware.org/systemtap/wiki)), [`perf`](https://en.wikipedia.org/wiki/Perf_(Linux)), and [`sysdig`](https://github.com/draios/sysdig).
@ -502,7 +502,7 @@ A few examples of piecing together commands:
- `id`: user/group identity info
- `sar`: historic system stats
- [`sar`](http://sebastien.godard.pagesperso-orange.fr/): historic system stats
- [`iftop`](http://www.ex-parrot.com/~pdw/iftop/) or [`nethogs`](https://github.com/raboof/nethogs): network utilization by socket or process