John Wendel wrote:
Ron Yorston wrote:
John Wendel wrote:
OK, I ran it again. "time prelink -av --force > foo"
I took 2 minutes 42 seconds, CPU was 16 seconds. Again, only one line
in the output file.
This is very puzzling. What happens if you run "prelink -uav" first,
to undo any existing prelinking?
Ron
[1] Ran "prelink -uav". It ran for 2 minutes 45 seconds and produced a
lot of disk noise but no output.
[2] Rebooted.
[3] Ran "prelink -av --force". Same result as before, it ran for a few
minutes and produced 1 line of output.
I checked /usr/bin and /usr/lib, the timestamps on the files haven't
been updated. Does a normal prelink run cause the file timestamps to be
changed?
I'm baffled! Any more suggestions?
Regards,
John
Here are my results:
# prelink -ua
# date > prelink.out
# prelink -av >> prelink.out
# date >> prelink.out
# cat prelink.out
Thu Oct 13 12:50:07 CDT 2005
Laying out 550 libraries in virtual address space 00101000-50000000
Assigned virtual address space slots for libraries:
[3640 lines cut]
Prelinking /usr/bin/renice
Thu Oct 13 13:14:33 CDT 2005
That's 24 minutes of solid activity, during which time starting
a new shell took 15 seconds.
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
