>>> On 07 March 2007 at 13:18, in message
<[EMAIL PROTECTED]>,
Morten Bjørnsvik <[EMAIL PROTECTED]> wrote:

> |All I need to do now, is work out why ZMD takes so flipping 
> |long to install patches regardless of it's NICEness... (come 
> |back YaST, all is forgiven !)
> 
> Mono is the root to all evil.

They used to say the same about Java...

> I had the same problem with beagle. 100% cpu load when it indexes.
> I find it strange because all indexing Should be io-bound.

I'd noticed that as well. It really only hits my machines after they've first 
been built. After that I never notice, so I don't care (Although I might notice 
now that ZMD is under control)

But here's another thought: ZMD & Beagle indexing are background tasks. So why 
do they either not have code in them to detect & reduce system load, or get 
fired off at a lower priority. I mean, this is back software engineering/system 
administration. Hello ?!? Anyone home ?

GTG


--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to