this post was submitted on 16 Dec 2025
165 points (98.2% liked)

Linux

60406 readers
922 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago
MODERATORS
 

I've been setting up a new Proxmox server and messing around with VMs, and wanted to know what kind of useful commands I'm missing out on. Bonus points for a little explainer.

Journalctl | grep -C 10 'foo' was useful for me when I needed to troubleshoot some fstab mount fuckery on boot. It pipes Journalctl (boot logs) into grep to find 'foo', and prints 10 lines before and after each instance of 'foo'.

you are viewing a single comment's thread
view the rest of the comments
[–] demonsword@lemmy.world 5 points 1 week ago (2 children)

Something that really improved my life was learn to properly use find, grep, xargs and sed. Besides that, there are these two little 'hacks' that are really handy at times...

1- find out which process is using some local port (i.e. the modern netstat replacement):

$ ss -ltnp 'sport = :<port-number>'

2- find out which process is consuming your bandwidth:

$ sudo nethogs

[–] Ephera@lemmy.ml 3 points 1 week ago

I always just do ss -ltnp | grep <port-number>, which filters well enough for my purposes and is a bit easier to remember...

[–] eli@lemmy.world 2 points 1 week ago

You can do "ss -aepni" and that will dump literally everything ss can get its hands on.

Also, ss can't find everything, it does have some limitations. I believe ss can only see what the kernel can see(host connections), but tcpdump can see the actual network flow on the network layer side. So incoming, outgoing, hex(?) data in transit, etc.

I usually try to use ss first for everything since I don't think it requires sudo access for the majority of its functionality, and if it can't find something then I bring out sudo tcpdump.