Proposed image for the 3rd article in the series is attached:

Reminder to myself, usage examples might be:

1. Finding open file by user or process
2. identify open network connections via sockets
3. lsblk -f/h/d

@andreashaerter Any movement on this part of your series? It gets some good comments.

@rlengland I started writing the article. Maybe I finished a draft within the next ~2h. If not, I will finish it within the next 2-5 days.

:question: :smile:

@andreashaerter How are you progressing on Part 3 of you series?

Sorry for being that late. Finally, after another hour, the draft: https://fedoramagazine.org/?p=40959&preview=true&preview_id=40959

@andreashaerter The article looks pretty good after my first pass.

One question. The very last sentence in the last paragraph implies that there is going to be another article in the series. This is fine if that is true, but if not, perhaps it should be removed?

Yes, this was my understanding. Two possible topics (=if this sounds ok for you, just create two issues here for me?) coming into my mind:

• lslogins & losmod (even if they are simple, just to remind people they exists :D) and then stop with the ls*-familiy
• free and vmstat:
  • Using free to check RAM and swap usage, and interpreting output (available, used, and free memory)
  • Differences between buffers/cache and actual used memory
  • vmstat for viewing system performance (memory, CPU, I/O, etc.)
  • Breaking down the key metrics in vmstat, some kind of practical examples / diagnosing memory leaks or performance bottlenecks

When they are done, start with the whole *top familiy

@andreashaerter That plan sounds good. Thanks for the clarification.

This article is scheduled for publication on 11 Sept.

Thanks. Looking forward to your next article.