On 4 September 2013 21:59, Michał Górny <mgo...@gentoo.org> wrote: > And how are you going to implement this? I doubt that fd/vt input has > any sort of 'writing process id' indicator. >
In one terminal: cat -vET In another: pgrep -x cat # 199935 ls -la /proc/199935/fd/ dr-x------ 2 kent kent 0 Sep 4 23:29 . dr-xr-xr-x 8 kent kent 0 Sep 4 23:28 .. lrwx------ 1 kent kent 64 Sep 4 23:29 0 -> /dev/pts/3 lrwx------ 1 kent kent 64 Sep 4 23:29 1 -> /dev/pts/3 lrwx------ 1 kent kent 64 Sep 4 23:29 2 -> /dev/pts/3 So you can certainly get the information the ohter way round. now... Term 1: $ tty /dev/pts/3 $ cat -vET Term 2: for i in /proc/[0-9]*; do cmd=$(cat $i/comm); for j in $i/fd/*; do echo -n "$cmd:$j:"; readlink $j ; echo ; done done | grep "pts/3" bash:/proc/159261/fd/0:/dev/pts/3 bash:/proc/159261/fd/1:/dev/pts/3 bash:/proc/159261/fd/2:/dev/pts/3 bash:/proc/159261/fd/255:/dev/pts/3 gvim:/proc/175475/fd/0:/dev/pts/3 gvim:/proc/175475/fd/1:/dev/pts/3 gvim:/proc/175475/fd/2:/dev/pts/3 gvim:/proc/175642/fd/0:/dev/pts/3 gvim:/proc/175642/fd/1:/dev/pts/3 gvim:/proc/175642/fd/2:/dev/pts/3 gvim:/proc/199494/fd/0:/dev/pts/3 gvim:/proc/199494/fd/1:/dev/pts/3 gvim:/proc/199494/fd/2:/dev/pts/3 cat:/proc/207567/fd/0:/dev/pts/3 cat:/proc/207567/fd/1:/dev/pts/3 cat:/proc/207567/fd/2:/dev/pts/3 I see. I have a few gvim instances also reading/writing to that terminal I didn't know about, interesting. -- Kent
