On Mon, Feb 18, 2008 at 03:13:35PM +1030, Daniel O'Connor wrote: >I didn't realise that the file descriptor used to write tracing data out >was 'owned' by the process being traced, I always thought ktrace did. Unlike truss/ptrace type tools, ktrace just sets a flag in the process that tells the kernel to generate ktrace records. This is more obvious when you use the 'ktrace -p PID' form. On Mon, 18 Feb 2008, Giorgos Keramidas wrote: >> It is probably easy to add an -F flag to ktrace/kdump which would >> inhibit the check for a `regular' file, so you could then write: >> >> ( ktrace -aF -f /dev/stdout ls ) | \ >> kdump -F -f /dev/stdin I don't think stdin/stdout is practical here but supporting named pipes sounds like it would be useful. >I guess it couldn't be moved to ktrace without rearchitecting how >ktracing works so the ktrace process sticks around writing stuff out to >disk. And from what I've seen of the innards of ktrace, the re-architecting would be quite significant. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour.
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:27 UTC