<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>172543</bug_id>
          
          <creation_ts>2007-03-28 10:33 0000</creation_ts>
          <short_desc>sys-devel/prelink - cronjob deletes manually-prelinked cache</short_desc>
          <delta_ts>2007-03-30 05:57:36 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Ebuilds</component>
          <version>unspecified</version>
          <rep_platform>All</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>zarhan@iki.fi</reporter>
          <assigned_to>toolchain@gentoo.org</assigned_to>
          

      

      
          <long_desc isprivate="0">
            <who>zarhan@iki.fi</who>
            <bug_when>2007-03-28 10:33:04 0000</bug_when>
            <thetext>I hadn&apos;t even noticed that prelink, after an update, installed a cronjob. My updating procedure has usually consisted, after emerge -uvDaN world &amp;&amp; emerge --depclean &amp;&amp; revdep-rebuild of prelinking with prelink -avmR.

I was wondering, why after every world-run, even if only a few packages got updated my prelink went through the entire system. Then I found this cronjob:

----
if [ &quot;$PRELINKING&quot; != yes ]; then
  if [ -f /etc/prelink.cache ]; then
    echo /usr/sbin/prelink -uav &gt; /var/log/prelink.log
    /usr/sbin/prelink -uav &gt;&gt; /var/log/prelink.log 2&gt;&amp;1 \
      || echo Prelink failed with return value $? &gt;&gt; /var/log/prelink.log
    rm -f /etc/prelink.cache
    # Restart init if needed
    [ -n &quot;$(find `ldd /sbin/init | awk &apos;NF == 4 { print $3 }&apos;` /sbin/init -ctime -1 2&gt;/dev/null )&quot; ] &amp;&amp; /sbin/telinit u
  fi
  exit 0
fi
----

 and then read description at conf.d/prelink

----
# Set this to no to disable prelinking altogether
# (if you change this from yes to no prelink -ua
# will be run next night to undo prelinking)
PRELINKING=no
---

 Checked documentation at http://www.gentoo.org/doc/en/prelink-howto.xml

----
sys-devel/prelink-20060213 and later install a cron job in /etc/cron.daily/prelink. To enable it, edit the configuration file /etc/conf.d/prelink. This will run prelink daily in the background, as needed, saving you running the command manually.
-----

Now, the way I&apos;m understanding the docs, the *intended* functionality is that you can still run prelink manually instead of cron un-prelinking everything at next cron-run. Why is there the &quot;prelink -uav&quot;?

Right now I deleted the entire cronscript, but maybe the conf.d/prelink should contain a third value &quot;manual&quot;, which would be the default - so it wouldn&apos;t automatically prelink or un-prelink..I don&apos;t want to remember to remove the cronscript everytime prelink gets updated.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>brendlerjg@gmail.com</who>
            <bug_when>2007-03-28 17:35:41 0000</bug_when>
            <thetext>A second user&apos;s perspective.  I like this scrpt!  But I do concur.  I initially went through the same thought process (although for me it was right after install, when I read the elog notice in my email).  

One of these two things should be:

either (a) 3 branches in the script: off, manual, and automatic;
or (b) the script should be initially installed commented out

Also, many thanks for fixing the kde lines already! :)</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>vapier@gentoo.org</who>
            <bug_when>2007-03-30 05:57:36 0000</bug_when>
            <thetext>added to cvs, thanks for the idea !

# Control prelinking behavior in the cronjob.
#  yes - automatically prelink the system
#  no  - automatically un-prelink the system
#  &quot;&quot;  - do nothing at all (user manages)
# (if you change this from yes to no prelink -ua
# will be run next night to undo prelinking)
PRELINKING=&quot;&quot;</thetext>
          </long_desc>
      
    </bug>

</bugzilla>