+++ This bug was initially created as a clone of Bug #154575 +++ Description of problem: crontab truncates file names greater than 100 characters. Version-Release number of selected component (if applicable): vixie-cron-3.0.1-75.1 How reproducible: Consistently Steps to Reproduce: 1. Create directory structure greater than 90 characters, for example: 'mkdir -p /tmp/smartfilter_da_ifs_4.0.0.00_16_redhat_enterprise_i386/smartfilter_da_ifs_4.0.0.00_16_redhat_enterprise_i386/ 2. Clone root crontab into new directory: 'crontab -l > /tmp/smartfilter_da_ifs_4.0.0.00_8_redhat_enterprise_i386/smartfilter_da_ifs_4.0.0.00_8_redhat_enterprise_i386/test.crontab' 3. Attempt to install newly cloned crontab: 'crontab /tmp/smartfilter_da_ifs_4.0.0.00_8_redhat_enterprise_i386/smartfilter_da_ifs_4.0.0.00_8_redhat_enterprise_i386/test.crontab' Actual results: crontab reports file not found: # crontab /tmp/smartfilter_da_ifs_4.0.0.00_16_redhat_enterprise_i386/smartfilter_da_ifs_4.0.0.00_16_redhat_enterprise_i386/test.crontab /tmp/smartfilter_da_ifs_4.0.0.00_16_redhat_enterprise_i386/smartfilter_da_ifs_4.0.0.00_16_redhat_ente: No such file or directory Expected results: crontab accepts filenames greater than 100 characters. Additional info: In Red Hat Enterprise 4.0, this issue exists, however, crontab reports that the filename is too long. # crontab /tmp/smartfilter_da_ifs_4.0.0.00_16_redhat_enterprise_i386/smartfilter_da_ifs_4.0.0.00_16_redhat_enterprise_i386/test.crontab crontab: usage error: filename too long Though it doesn't say how long by.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2005-361.html