Here's the output of running the script with #!/bin/bash -x
/etc/cron.daily/prelink:
+ . /etc/sysconfig/prelink
++ PRELINKING=yes
++ PRELINK_OPTS=-mR
++ PRELINK_FULL_TIME_INTERVAL=14
+ renice +19 -p 3697
+ '[' yes '!=' yes ']'
+ '[' '!' -f /etc/prelink.cache -o -f /var/lib/misc/prelink.force ']'
+ grep -q '^prelink-ELF0.[0-2]' /etc/prelink.cache
++ find /var/lib/misc/prelink.full -mtime -14
+ '[' -n 14 -a /var/lib/misc/prelink.full = /var/lib/misc/prelink.full
']'
+ PRELINK_OPTS=-mR -q
+ echo /usr/sbin/prelink -av -mR -q
+ /usr/sbin/prelink -av -mR -q
+++ ldd /sbin/init
+++ awk '{ print $3 }'
++ find '(0x009ba000)' /lib/libselinux.so.1 /lib/tls/libc.so.6
/lib/ld-linux.so.2 /sbin/init -ctime -1
+ '[' -n '' ']'
+ exit 0
On Thu, 2004-08-05 at 21:10, netmask wrote:
> Well.. That's strange.. I would recommend adding a -x to the top of the
> prelink script (#!/bin/bash -x) and then looking at the output log file (or
> sending the appropriate snippet here) to investigate further.
>
>
> --
> netmask
>
> > Amit Bapat (amitbapat@xxxxxxxxxxxxx) composed today:
>
> > On Thu, 2004-08-05 at 10:09, netmask wrote:
> >>> What happens when you run the following by hand:
> >>>
> >>> /usr/sbin/prelink -av -f
> >>> (May take a while)
> >>
> >> Sorry, that should be:
> >>
> >> /usr/sbin/prelink -av -mR -f
> >>
> > This runs just fine when I run it on command line as 'root'.
> >
> >>> and then
> >>>
> >>> /usr/sbin/prelink -av -mR -q
> >>
> > This too runs fine without problem on command line as 'root'.
> >
> >
> >> The reason im having you try both.. is -f is a 'full' and -q is a 'quick'..
> >> depending on how long its been since you ran a 'full', the script may be
> >> trying to do a full or a quick.. so for testing, i wanted to see that both
> >> would run.
> >>
> >
> >
> > --
> > fedora-list mailing list
> > fedora-list@xxxxxxxxxx
> > To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
> >
>
