>> I've experienced, and seen a few references to similar experiences on
>> the web, saned consuming all available CPU when in use.
>>
>> After running a strace while it was doing this, and examining the
>> source to saned, it appears that it is locked in a tight select loop
>> with no timeout.
>
>
es to other processes.
Was this a deliberate design choice?
If it is a flaw, what is the best way to get it fixed? Should I fix it and
submit a patch, or try to take it up with whomever maintains that
particular frontend?
Regards,
Jay Guerette
