# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 10
# self = https://watcher.sour.is/conv/67tvvwa
prologic
twtxt.net
View Thread
Anyone have any ideas how you might identify processes (pids) on Linux machine that are responsible for most of the Disk I/O on that machine and subsequently causing high I/O wait times for other processes? 🤔

**Important bit:** The machine has no access to the internet, there are hardly any standard tools on it, etc. So I have to get something to it "air gapped". I have terminal access to it, so I can do interesting things like, base64 encode a static binary to my clipboard and paste it to a file, then base64 decode it and execute. That's about the only mechanisms I have.
prologic
twtxt.net
View Thread
Anyone have any ideas how you might identify processes (pids) on Linux machine that are responsible for most of the Disk I/O on that machine and subsequently causing high I/O wait times for other processes? 🤔

**Important bit:** The machine has no access to the internet, there are hardly any standard tools on it, etc. So I have to get something to it "air gapped". I have terminal access to it, so I can do interesting things like, base64 encode a static binary to my clipboard and paste it to a file, then base64 decode it and execute. That's about the only mechanisms I have.
prologic
twtxt.net
View Thread
Anyone have any ideas how you might identify processes (pids) on Linux machine that are responsible for most of the Disk I/O on that machine and subsequently causing high I/O wait times for other processes? 🤔

**Important bit:** The machine has no access to the internet, there are hardly any standard tools on it, etc. So I have to get something to it "air gapped". I have terminal access to it, so I can do interesting things like, base64 encode a static binary to my clipboard and paste it to a file, then base64 decode it and execute. That's about the only mechanisms I have.
abucci
anthony.buc.ci
View Thread
@prologic iotop
prologic
twtxt.net
View Thread
@abucci already tried very hard to get that on there but it spews errors 😢
prologic
twtxt.net
View Thread
@abucci already tried very hard to get that on there but it spews errors 😢
prologic
twtxt.net
View Thread
@abucci already tried very hard to get that on there but it spews errors 😢
movq
www.uninformativ.de
View Thread
@prologic That’s a tough one. Newer versions of htop have a second panel that shows I/O (press Tab to get there), maybe that’s already installed?

You could also run ps aux and search for processes in the D state. I/O-bound processes tend to show up there.
movq
www.uninformativ.de
View Thread
@prologic That’s a tough one. Newer versions of htop have a second panel that shows I/O (press Tab to get there), maybe that’s already installed?

You could also run ps aux and search for processes in the D state. I/O-bound processes tend to show up there.
movq
www.uninformativ.de
View Thread
@prologic That’s a tough one. Newer versions of htop have a second panel that shows I/O (press Tab to get there), maybe that’s already installed?

You could also run ps aux and search for processes in the D state. I/O-bound processes tend to show up there.