como usar o topo e livre para ver o que está sobrecarregando o sistema?

Question

Não consegui extrair o resultado do topo, mas tive muitas, muitas instâncias do leafnode listadas. Eles não estavam usando, individualmente, muitos recursos. Talvez em conjunto eles estivessem atolando o sistema.

Logs de /var/log/news/news.err show:

Dec 22 01:26:16 doge fetchnews[4121]: Cannot obtain lock file, aborting.
Dec 22 01:28:12 doge leafnode[3950]: Cannot write to client: Broken pipe
Dec 22 01:28:12 doge leafnode[3964]: Cannot write to client: Broken pipe
Dec 22 01:28:12 doge leafnode[3951]: Cannot write to client: Broken pipe
Dec 22 01:28:13 doge leafnode[3976]: Cannot write to client: Broken pipe
Dec 22 01:28:13 doge leafnode[3942]: Cannot write to client: Broken pipe
Dec 22 01:28:13 doge leafnode[3944]: Cannot write to client: Broken pipe
Dec 22 01:28:15 doge leafnode[3977]: Cannot write to client: Broken pipe
Dec 22 01:28:15 doge leafnode[3949]: Cannot write to client: Broken pipe
Dec 22 01:28:15 doge leafnode[3974]: Cannot write to client: Broken pipe
Dec 22 01:28:15 doge leafnode[3965]: Cannot write to client: Broken pipe
Dec 22 01:28:15 doge leafnode[3975]: Cannot write to client: Broken pipe
Dec 22 01:28:15 doge leafnode[3952]: Cannot write to client: Broken pipe
Dec 22 01:28:16 doge leafnode[3945]: Cannot write to client: Broken pipe
Dec 22 01:28:16 doge leafnode[3963]: Cannot write to client: Broken pipe
Dec 22 01:28:17 doge leafnode[3943]: Cannot write to client: Broken pipe
Dec 22 01:28:17 doge leafnode[3966]: Cannot write to client: Broken pipe
Dec 22 01:28:33 doge leafnode[3905]: Cannot write to client: Broken pipe
Dec 22 01:28:33 doge leafnode[3909]: Cannot write to client: Broken pipe
Dec 22 01:28:40 doge leafnode[3904]: Cannot write to client: Broken pipe
Dec 22 01:28:40 doge leafnode[3910]: Cannot write to client: Broken pipe
Dec 22 01:28:43 doge leafnode[3903]: Cannot write to client: Broken pipe
Dec 22 01:28:45 doge leafnode[3879]: Cannot write to client: Broken pipe
Dec 22 01:28:45 doge leafnode[3880]: Cannot write to client: Broken pipe
Dec 22 01:28:45 doge leafnode[3902]: Cannot write to client: Broken pipe
Dec 22 01:28:46 doge leafnode[3908]: Cannot write to client: Broken pipe
Dec 22 01:28:48 doge leafnode[3896]: Cannot write to client: Broken pipe
Dec 22 01:28:48 doge leafnode[3882]: Cannot write to client: Broken pipe
Dec 22 01:28:48 doge leafnode[3895]: Cannot write to client: Broken pipe
Dec 22 01:28:48 doge leafnode[3893]: Cannot write to client: Broken pipe
Dec 22 01:28:48 doge leafnode[3911]: Cannot write to client: Broken pipe
Dec 22 01:28:48 doge leafnode[3881]: Cannot write to client: Broken pipe
Dec 22 01:28:48 doge leafnode[3894]: Cannot write to client: Broken pipe
thufir@doge:~$ 
thufir@doge:~$ date
Thu Dec 22 01:36:22 PST 2016
thufir@doge:~$ 

não sei o que fazer com isso. Existe alguma maneira com top ou free para ver até que ponto leafnode , ou fetchnews ou texpire , estão usando recursos? Esses três programas fazem parte do servidor de notícias leve NNTP leafnode. Não deveria ser tão intenso assim.

    

Answer 1

Eu acho htop mais fácil de usar

sudo apt-get install htop

Ele exibirá o uso da CPU, bem como da memória, e você poderá classificar por qualquer uma das colunas na exibição. Isso pode facilitar a identificação de quais programas / processos estão usando seus recursos.

Free -m exibe o uso de memória no Mibibytes. A coluna usada corresponde aproximadamente aos valores exibidos no topo da janela htop (os dados usados para combinar melhor em versões anteriores do Ubuntu, antes de 16.04 LTS).

$ free -m
              total        used        free      shared  buff/cache   available
Mem:           4041         869        1813          33        1358        2728
Swap:         16399           0       16399