Issue in glibc in FC3T3 ?

[Kim Lux]

I know everyone has worked hard on scheduling, etc and I appreciate all
they've done.  I'd just love to see process have a "throttle" attribute
such that they are limited to how much of various resources they are
allowed to consume.  (Maybe this is already in the new schedulers ?)  It
would than be nice if cron jobs had a throttle parameter.  (I know about
nice.)

There would be nothing wrong with cron jobs such as prelink running at
10 to 30% cpu for 10 minutes or so.

Prelink just ran on my new fc3rc3 installation.  It took about 5 minutes
at high CPU usage.  I believe this is the first time it ran on the new
installation.  I can't say if yesterday's episode was warranted or not.
I'll assume it was until I see something that appears out of the
ordinary. 

Kim

On Fri, 2004-10-29 at 17:09 +0200, Kyrre Ness Sjobak wrote:
> tor, 28.10.2004 kl. 17.56 skrev Kim Lux (Mr.):
> > I just ran prelink manually.  cpu usage never went over 3%.  It was done
> > in 2 minutes. 
> > 
> > It was not an issue that prelink was running.  I think it was an issue
> > that is was running at 80% cpu resources. 
> *snip*
> 
> Hmm? On my computers (those who get shutdown at night), prelink usually
> starts about 1-½ hour after i booted it, and it has two "phases" - a
> "little CPU" phase, and the "eat as much CPU as you can get" phase.
> Thanks god for multitasking. It usually last something like 5 minutes.
> This is on core 2, and i think core 1 was similar.
> 
> Another überannoying cronjob, is the updatedb one. whytheh*** does
> anacron have to run it?!? It also takes about 5 minutes, and it is
> almost impossible to lauch programs in a resonable time when it is
> running...
>