On Mon, 2006-02-20 at 08:24 -0800, thewade wrote:
This is all well and good but you're only talking about CPU. Disk
I/O is another story entirely. If your WM starts doing some I/O that
you weren't aware of you may get an xrun because you couldn't access the
disk in time. This is the reason that I kill syslogd before I record.
Granted, generally speaking you'll do OK due to the priority of your
process but disk I/O takes a certain amount of time and you can't
interrupt it once it's gone to the disk.
Jan 'Evil Twin' Depner
The Fuzzy Dice
"As we enjoy great advantages from the invention of others, we should be
glad of an opportunity to serve others by any invention of ours, and
this we should do freely and generously."
Benjamin Franklin, on declining patents offered by the governor of
Pennsylvania for his "Pennsylvania Fireplace", c. 1744