Diego Augusto Molina <[email protected]> writes: > Here's my suggestion: > > # ss -nlpt | grep 3722 > > That should include your offending instance of socat listening on TCP > 3722, stating the PID that has the resource (a.k.a., the socat process > that opened the port). Killing that PID blindly might not always do > the trick (e.g. "while true; do socat ...; sleep 1; done") so you may > want to kill parents/children too. With that PID in mind use "ps faux" > to navigate through the process tree. My way is:
Yes, this didn't help here as the socket was in TIME-WAIT. ss -napt however works. -- Leah Neukirchen <[email protected]> http://leah.zone -- You received this message because you are subscribed to the Google Groups "voidlinux" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/voidlinux/871s47wigo.fsf%40vuxu.org. For more options, visit https://groups.google.com/d/optout.
