Bug 163885 - crontab truncates file names greater than 100 characters.
Summary: crontab truncates file names greater than 100 characters.
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: vixie-cron
Version: 4.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Jason Vas Dias
QA Contact: Brock Organ
Depends On: 154575
Blocks: 156322
TreeView+ depends on / blocked
Reported: 2005-07-21 19:34 UTC by Jason Vas Dias
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version: RHSA-2005-361
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-10-05 12:35:09 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2005:361 qe-ready SHIPPED_LIVE Low: vixie-cron security update 2005-10-05 04:00:00 UTC

Description Jason Vas Dias 2005-07-21 19:34:38 UTC
+++ 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):


How reproducible:


Steps to Reproduce:
1. Create directory structure greater than 90 characters, for example: 'mkdir -p
2. Clone root crontab into new directory: 'crontab -l >
3. Attempt to install newly cloned crontab: 'crontab

Actual results:

crontab reports file not found: 

# crontab

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

crontab: usage error: filename too long

Though it doesn't say how long by.

Comment 5 Red Hat Bugzilla 2005-10-05 12:35:09 UTC
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.


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