I have a similar problem with the popular 'dig' utility. Running 'dig 2>
/dev/null > /dev/null' suffices to cause disk activity, even when run many
times in succession.
As far as stracing can tell (dig is multithreaded), there is no reason for
this.
Regards,
bert
-- http://www.PowerDNS.com Versatile DNS Software & Services http://www.tk the dot in .tk http://lartc.org Linux Advanced Routing & Traffic Control HOWTO - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/