I was playing around with kde 3.2 and a crashing artsd was locking up
my sound system - any further attempts to use sound from gnome or xmms
or anything failed with
/dev/dsp - device busy
messages. fstat and lsof showed nothing holding the device. A reboot
would fix it, but why reboot
When people talk about optimizing mod_perl shared memory, they are not
referring to System V type shared memory as seen by ipcs. They are
talking about memory shared by virtue of a process fork - this is
effectively read only memory. The net effect is that a process may
appear to be 20 meg, but
I have disk access on my machine every 2 seconds, is there a way to
figure out which process is the guilty one?
Also, I have another drive which I let spin down - it spins up
occasionally, I don't know why. I would like to figure out what
program(s) are accessing the other disk.
This is on
