| |||||||||||||
Announcing a new utility: 'trace'Announcing a new utility: 'trace'Posted Nov 19, 2010 17:15 UTC (Fri) by adamgundy (subscriber, #5418)In reply to: Announcing a new utility: 'trace' by adamgundy Parent article: Announcing a new utility: 'trace' actually, what would *really* good would be if trace (or strace) could figure out the FD *even if* it didn't see it opened (ie: you attached to the process later on) - combining a bit of lsof functionality with the tracer.
(Log in to post comments)
Announcing a new utility: 'trace' Posted Nov 26, 2010 15:37 UTC (Fri) by i3839 (guest, #31386) [Link]
That's fairly easy because all you need is to read the /proc/$PID/fd/$FD symlink. That works great for files. For sockets it works less great, because it seems tricky to figure out which socket belongs to which fd.
|
|||||||||||||