Bug#446643: Info received (Bug#446643: saned is started twice with the same priority, one copy g

Renicing saned doesn't renice xsane automatically. Renicing one process influences only the future children. So your note is irrelevant. Look at setpriority(...) and/or sched_yield(). Good example for any of the saned copies: if(number_of_read_bytes==0) sched_yield();

Bug#446643: Info received (Bug#446643: saned is started twice with the same priority, one copy g

sasha mal [EMAIL PROTECTED] wrote: Hi, Renicing saned doesn't renice xsane automatically. Renicing one process influences only the future children. So your note is irrelevant. Because in this case, the frontend, as far as the mustek_pp backend is concerned, is saned itself and not xsane

Bug#446643: Info received (Bug#446643: saned is started twice with the same priority, one copy g

If you suppose that my suggestion is not applicable, it's not a reason to close the bug. 100% slowdown is a bug. What solutions are applicable and what are not applicable is a different question. ___ Join Excite! - http://www.excite.com The most