Timeline for netstat: See process name like in `ps aux`
Current License: CC BY-SA 3.0
21 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 27, 2019 at 12:30 | answer | added | allan | timeline score: 2 | |
| S Oct 24, 2016 at 8:13 | history | bounty ended | guettli | ||
| S Oct 24, 2016 at 8:13 | history | notice removed | guettli | ||
| Oct 24, 2016 at 8:11 | history | edited | guettli | CC BY-SA 3.0 |
added 424 characters in body
|
| Oct 22, 2016 at 3:18 | comment | added | Wildcard |
Does simply piping to full (as defined in my answer) qualify as "easy to use"? :)
|
|
| Oct 21, 2016 at 20:58 | answer | added | FloHimself | timeline score: 0 | |
| Oct 21, 2016 at 20:19 | answer | added | Wildcard | timeline score: 10 | |
| Oct 21, 2016 at 7:37 | history | edited | guettli | CC BY-SA 3.0 |
All answers work. Thank you very much for showing your unix knowledge. But up to now the answers are far too long/complicated.
|
| Oct 20, 2016 at 23:59 | comment | added | Totor |
If you use Linux, please not that netstat is deprecated in favor of ss. It has the same limitation as you point out, however.
|
|
| Oct 20, 2016 at 19:22 | answer | added | Zachary Brady | timeline score: 1 | |
| Oct 20, 2016 at 15:38 | answer | added | VenkatC | timeline score: 5 | |
| Oct 18, 2016 at 13:24 | answer | added | Iñaki Murillo | timeline score: 4 | |
| Oct 18, 2016 at 10:44 | history | edited | guettli | CC BY-SA 3.0 |
It seems that netstat can't do it. If you know how to do this with an other tool, then this is valid question, too. (But netstat based solutions are still prefered).
|
| Oct 18, 2016 at 8:33 | comment | added | toed | I am not sure if it is possible to see the full command line in netstat. I think it is reading the file /proc/13640/comm, and that is only showing the "master" name | |
| Oct 18, 2016 at 4:56 | history | tweeted | twitter.com/StackUnix/status/788242331635941376 | ||
| Oct 17, 2016 at 6:57 | comment | added | Satō Katsura |
Who said anything about switching. lsof has lots of features. On the other hand netstat is OS-dependent, and its features don't completely overlap with those of lsof. You should use both when appropriate.
|
|
| Oct 17, 2016 at 6:31 | comment | added | guettli | @SatoKatsura during the last years I mostly used netstat. Are there any other good reasons to switch? Up to now this question is the first feature I am missing. | |
| S Oct 17, 2016 at 6:30 | history | bounty started | guettli | ||
| S Oct 17, 2016 at 6:30 | history | notice added | guettli | Draw attention | |
| Oct 12, 2016 at 10:44 | comment | added | Satō Katsura |
Use lsof instead.
|
|
| Oct 12, 2016 at 9:41 | history | asked | guettli | CC BY-SA 3.0 |