On Mon, Mar 17, 2008 at 10:05 PM, Brendan Gregg - Sun Microsystems <[EMAIL PROTECTED]> wrote: > # ./keysniffer.d > Tracing... Hit Ctrl-C to end. > 2008 Mar 18 02:43:38 kbtrans_keyreleased: 0x79 y > 2008 Mar 18 02:43:38 kbtrans_keyreleased: 0x6f o > 2008 Mar 18 02:43:38 kbtrans_keyreleased: 0x75 u > 2008 Mar 18 02:43:39 kbtrans_keyreleased: 0x20 > 2008 Mar 18 02:43:39 kbtrans_keyreleased: 0x68 h > 2008 Mar 18 02:43:39 kbtrans_keyreleased: 0x61 a > 2008 Mar 18 02:43:39 kbtrans_keyreleased: 0x76 v > 2008 Mar 18 02:43:39 kbtrans_keyreleased: 0x65 e
I started down the path of using a similar technique some time ago (ssh sessions, not X) and found that I could not get proper ordering of the keystroke logging if I typed sufficiently fast. I suspect that the magnitude of this problem increases with the number of CPUs and workload on the system. If memory serves, I was on a lightly loaded T2000. My thoughts were to log a high resolution timer (ticks?) along with the tty and keystroke for reassembly later. -- Mike Gerdts http://mgerdts.blogspot.com/ _______________________________________________ dtrace-discuss mailing list [email protected]
