Bug 127350 - /etc/cron.daily/prelink will never invoke telinit -u
/etc/cron.daily/prelink will never invoke telinit -u
Product: Fedora
Classification: Fedora
Component: prelink (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Depends On:
  Show dependency treegraph
Reported: 2004-07-06 18:00 EDT by Graham King
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version: 0.3.2-5
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-10-02 13:47:14 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Graham King 2004-07-06 18:00:06 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510

Description of problem:
/etc/cron.daily/prelink contains 2 occurrences of
    # Restart init if needed
    [ -n "$(find `ldd /sbin/init | awk '{ print $3 }'` /sbin/init \
          -ctime -1 2>/dev/null )" ] && /sbin/telinit u

ldd /sbin/init  output is 
    linux-gate.so.1 =>  (0x002c0000)
    libselinux.so.1 => /lib/libselinux.so.1 (0x005e9000)
    libc.so.6 => /lib/tls/libc.so.6 (0x00784000)
    /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x0076b000)
the first line of which causes find(1) to error.

The error message and lack of output on stdout will ensure that [ -n
"$(find .... 2>/dev/null)" ] is always false, so telinit will never be

Version-Release number of selected component (if applicable):
prelink-0.3.2-1  SysVinit-2.85-25

How reproducible:
Didn't try

Steps to Reproduce:
1. Inspect code of /etc/cron.daily/prelink
2. Follow steps in the Description.

Additional info:
Comment 1 Jakub Jelinek 2004-07-07 10:33:26 EDT
    [ -n "$(find `ldd /sbin/init | awk 'NF == 4 { print $3 }'` /sbin/init \
          -ctime -1 2>/dev/null )" ] && /sbin/telinit u
should cure it.
Will build prelink-0.3.2-4.
Comment 2 Graham King 2004-07-08 05:46:28 EDT
That should be fine, provided that the problem really is with the
script, and not with the output of ldd /sbin/init.

Note You need to log in before you can comment on or make changes to this bug.