tech-kern archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

identifying I/O pigs


As I undertand, when we see a NetBSD box on its knees because of high 
disk I/O, we have no way to find the offending process, and within 
the process. Am I right? If I am, it would be a nice feature to add.
Anyone already thought about it?

Emmanuel Dreyfus

Home | Main Index | Thread Index | Old Index