You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,9 +39,9 @@ avahi-daemon (pid 655 user avahi)
39
39
* Explaining wireguard and vxlan listening ports
40
40
41
41
More specifically
42
-
*`ss` has a nice short command, but then you need a lot of arguments. But which? `-lpunt`? (Though of course, `ss` can do things `lls` can't, like printing established connections or unix sockets.)
42
+
*`ss` has a nice short command, but then you need a lot of arguments. `-plut0wn` maybe? (Though of course, `ss` can do things `lls` can't, like printing established connections or unix sockets.)
43
43
*`ss` output requires ~160 columns, while `lls` makes do with ~60.
44
44
*`ss` output order is unfathomable.
45
-
*For interpreters, `ss` will just display the command name, e.g. `python` or `node`.
45
+
*`ss` will just display the command name, e.g. `python` or `node`, but not what script is running.
46
46
`lls` tries to parse the command line of the interpreters and display the script name where possible.
47
47
*`ss` prints almost no information for listening ports belonging to WireGuard or VXLAN interfaces, and what it prints is more confusing than helpful.
0 commit comments