Description of problem: cronjob throws an error message: /etc/cron.daily/readahead.cron: ls: cannot access /etc/readahead.d/*.later: No such file or directory Looking at the code, it appears that the script and the packaging of the readahead.d directory are confused whether the files are '*.later' or 'later.*'. I've attached a patch to change the script to match what's actually in the directory. Alternatively, the files could be renamed to match what the script is expecting. Version-Release number of selected component (if applicable): readahead-1.4.5-1.fc10.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 315457 [details] Make readahead.cron look for the right filenames...
I also get an error about /etc/readahead.d/*.early: /etc/cron.daily/readahead.cron: ls: cannot access /etc/readahead.d/*.early: No such file or directory ls: cannot access /etc/readahead.d/*.later: No such file or directory
I see it too. Would probably be better to redirect stderr of the "ls" to /dev/null as it's seemingly not at all unlikely that some of the files are not there (for example, I have neither *.later or later.*). Also, the srpm contains default.{early,later} which are copied into place in %prep and then later simply removed in %install - I suppose those could be just dropped.
Well, really an output from 'ls' should not be used in scripts (unless there are really good reasons and this does not seem to be the case). Quite possibly something like that was intended: FLS=$( shopt -s nullglob; echo $READAHEAD_BASE/*$LTYPE* ) although I am not entirely sure how to guess from what I see. The main loop of this script may look somewhat like that (with possibly different globbing; I cannot really tell): shopt -s nullglob for LTYPE in $TYPES; do FLS=$(echo $READAHEAD_BASE/*custom.$LTYPE) [ -n "$FLS" ] || FLS=$(echo $READAHEAD_BASE/*$LTYPE*) [ -n "$FLS" ] || continue $READAHEAD_CMD ... done
will change to a better globbing. rawhide pipes to /dev/null