On Apr 2, 2009, at 11:07 PM, Emmanuel Dreyfus wrote:
Apart from killing the processes one by one (there are many), is there away to discover which process is the I/O hog?
Perhaps "top -m io" would be helpful (assuming that option is supported on NetBSD)?
Regards, -- -Chuck