Agreed. Prelink was running for 10 minutes at high cpu usage. I think there is an issue here. See the email I just sent. On Thu, 2004-28-10 at 11:53 -0400, Jakub Jelinek wrote: > On Thu, Oct 28, 2004 at 09:46:28AM -0600, Kim Lux (Mr.) wrote: > > I never even thought it would be a cron job ! > > > > This doesn't explain the top process running as root though. > > > > Furthermore, prelink ran for about 10 minutes at 80+%. It is running on > > an otherwise unloaded 3.2GHz P4 with 1GB RAM. I think there was > > something wrong with it. > > If you have upgraded glibc, then nothing is wrong about prelink running > for 10 or even 30 minutes depending on how many programs you have instaled > and how fast the CPU is. > When glibc is upgraded, prelink needs to re-prelink all binaries on your > system and all libraries they are using, so in the order of several > thousands of binaries and libraries. > On the other side, when nothing got upgraded within last day, prelink > when not running in its fortnight non-quick mode should take just a few > seconds, if caches are really cold worst case a minute or two. > > Jakub > -- Kim Lux (Mr.) <lux@xxxxxxxxxxxxxxxxxxx>