[go-nuts] filago: Monitor a Linux process' opening and closing of files, including Unix pipes and sockets

Does this have some advantage over truss (or under Linux, strace)? -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For

[go-nuts] filago: Monitor a Linux process' opening and closing of files, including Unix pipes and sockets

fuser(1) will tell you for a file netstat(1) -anp will do for sockets -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com.

[go-nuts] filago: Monitor a Linux process' opening and closing of files, including Unix pipes and sockets

Thanks! This should be very useful. Sometimes I want to know the inverted answer that which process is using a port or a file. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it,

[go-nuts] filago: Monitor a Linux process' opening and closing of files, including Unix pipes and sockets

Monitor open files (via /proc/pid) of a process. Lists time when it first sees the file open (which may be later than when the file actually opened, especially at startup of filago), and when it is no longer open. Stop running when target process ends. This includes anon_inode and tcp and