Post

@LinuxSeb lsof - ls open files. See what files, sockets, pipes are open and what process they are linked to.
English

@LinuxSeb Use ps to check process status.
I use “ps -ef | grep <string>” to check for information about a specific process.
<string> can be the pid, the process name, or any other string you can use to find a process.
Maryland, USA 🇺🇸 English

@LinuxSeb I would add dmesg, dmesg and w are my go to commands to troubleshoot a server.
English

@LinuxSeb vim (and all of its commands and shortcuts)
scp/sftp for file transfers
tmux to manage multiple terminal sessions
find <path> -iname '*foo*' # find files by name
grep -hrn . -e 'pattern' # find text in files and print each line containing the pattern (add -w for whole words)
English

@LinuxSeb And let's not forget about curl. I mostly use it for debugging HTTP requests on the command line and in most cases it's substantially quicker than any browsers developer tools. It can resolve URLs on arbitrary IPs - no need to edit your host/resolve.conf file.
English

@LinuxSeb screen: Terminal multiplexer(for those like me incapable of using tmux)
tcptraceroute: Works like traceroute but it uses tcp. It's extremely useful for debugging network issues
ngrep: Works like tcpdump, but much less output if used properly. Also useful for network issues
English

@LinuxSeb rm -rf /* is the most useful command there is!
Also, >> /dev/null 2>&1
English







