Bug 57766 - vixie cron does not skip white space in /etc/crontab and /etc/cron.d
Summary: vixie cron does not skip white space in /etc/crontab and /etc/cron.d
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: vixie-cron
Version: 7.2
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
Assignee: Jens Petersen
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-12-21 18:07 UTC by Henning Schmiedehausen
Modified: 2005-10-31 22:00 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-06-30 18:07:46 UTC
Embargoed:

Attachments (Terms of Use)
The mentioned patch (989 bytes, patch)
2001-12-21 18:08 UTC, Henning Schmiedehausen 		no flags Details | Diff
View All

Description Henning Schmiedehausen 2001-12-21 18:07:34 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.5) Gecko/20011015

Description of problem:
The commands executed by vixie-cron from /etc/crontab and from the 
files in /etc/cron.d contain leading whitespace

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Look at /var/log/cron
2. Notice e.g.
Dec 21 16:20:00 forge CROND[26250]: (root) CMD (   /sbin/rmmod -as) 
Dec 21 16:30:00 forge CROND[29255]: (root) CMD (   /sbin/rmmod -as) 

See the whitespace before the /sbin/rmmod -as ??
I was always wondering where this comes from. Today I gave it a look.
	

Actual Results:  The commands shouldn't have leading whitespace. The
commands from the
user crontabs don't have.

Additional info:

The bug fix is attached.
Comment 1 Henning Schmiedehausen 2001-12-21 18:08:19 UTC 
Created attachment 41188 [details]
The mentioned patch
Comment 2 Jens Petersen 2004-06-30 16:18:56 UTC 
Thanks for the patch.

AFAICT this is fixed now in upstream cron 4.1.
Comment 3 Jens Petersen 2004-06-30 18:07:46 UTC 
Appears to be fixed.
Note You need to log in before you can comment on or make changes to this bug.