I just ran a MySQL lookup process (written in Perl) as root prefixed
with idprio 1. I expected it to take a while, but not several
minutes. After a while I decided to abort it, so I typed ^c in its
`screen' window. From then on (either from the ^c point or the idprio
run, I know not which), I
On Sat, Nov 19, 2005 at 01:32:36PM -0500, Doug Lee wrote:
I just ran a MySQL lookup process (written in Perl) as root prefixed
with idprio 1. I expected it to take a while, but not several
minutes. After a while I decided to abort it, so I typed ^c in its
`screen' window. From then on
Any hidden hazards in rtprio then? I plan to use rtprio when
recording sound, so i/o bursts etc. won't cause things to be missed in
the recording.
Thanks much for the idprio heads-up.
And I do hope, sometime, to jump from 4 to 6 directly--though I also
plan to buy a new machine for that. I
