Description of problem: The PATH line in /etc/crontab currently looks like this: PATH=/sbin:/bin:/usr/sbin:/usr/bin /etc/anacrontab reads this way, however: PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin I can't imagine why the two would have different PATHs. I think /etc/crontab should also list /usr/local/sbin & bin. Version-Release number of selected component (if applicable): crontabs-1.10-1
Problem still exists in Red Hat 9 with crontabs-1.10-5
Still exists in Fedora Core 2 with crontabs-1.10-6
If you want a different $PATH in /etc/crontab, make it so ! That's what configuration files are for. There may be some systems that depend on /usr/local/*bin NOT being in the /etc/crontab $PATH. With PAM enabled in vixie-cron-4.1 the environment now comes from pam_env unless overridden by crontab file settings.
> There may be some systems that depend on /usr/local/*bin NOT > being in the /etc/crontab $PATH. Then why does /etc/anacrontab include /usr/local/*bin by default? anacron runs the very same scripts that cron does, but with /usr/local/*bin in the path! There is a bug here -- the only question is whether it is in /etc/crontab (i.e. it SHOULD list /usr/local/*bin) or in /etc/anacrontab (i.e. it SHOULDN'T list /usr/local/*bin). I would lean toward adding /usr/local/*bin to /etc/crontab since /usr/local/*bin is included in the PATH almost everywhere else.
Fedora Core 2 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC3 updates or in the FC4 test release, reopen and change the version to match.
Issue explained in comment #4 still exist in FC4. Shouldn't PATHs be the same in both files?
This is still the same in devel. I'm going to change the description to point out the problem rather than the proposed solution. :)
I am going to change the PATH in /etc/anacrontab to make the PATH the same as it is in /etc/crontab. The PATH in /etc/crontab should be sufficient. If not, then I belive the user can change add the missing item to his PATH in /etc/anacrontab.
The bug should be fixed in version anacron-2.3-39.fc6. Update for FC5 has been pushed (anacron-2.3-39.fc5).