Bug 170794 - cron misinterprets escaped percent signs
Summary: cron misinterprets escaped percent signs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: vixie-cron
Version: 3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jason Vas Dias
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On: 110189
Blocks: 161600
TreeView+ depends on / blocked
 
Reported: 2005-10-14 15:57 UTC by Jason Vas Dias
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version: RHSA-2005:0117
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-05-01 17:53:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jason Vas Dias 2005-10-14 15:57:04 UTC
+++ This bug was initially created as a clone of Bug #110189 +++

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Gecko/20031030

Description of problem:
cron seems to be misinterpreting backslash-escaped percent sign
characters in commands.  Normally, cron will replace a percent sign in
a command string with a newline.  While preceeding the percent sign
with a backslash prevents this replacement, it leaves the backslash.

Version-Release number of selected component (if applicable):
vixie-cron-3.0.1-76

How reproducible:
Always

Steps to Reproduce:
1. Create a crontab entry such as: 
@reboot date "+Rebooted at \%c" | mail -s reboot root
2. Reboot
3.
    

Actual Results:  root gets email saying:
Rebooted at \Sun Nov 16 13:59:47 2003


Expected Results:  root should get email saying:
Rebooted at Sun Nov 16 13:59:47 2003


Additional info:

-- Additional comment from jvdias on 2004-08-04 18:56 EST --
fixed in vixie-cron-4.1-+

Comment 1 Jason Vas Dias 2005-10-14 15:58:03 UTC
This bug is fixed with vixie-cron-4.1-8_EL3, available from:
  http://people.redhat.com/~jvdias/cron/RHEL-3
and should be considered for inclusion in RHEL-3-U7 .

Comment 3 Jason Vas Dias 2006-05-01 17:53:01 UTC
Fixed with vixie-cron-4.1-10.EL3, currently in RHEL-3-U7 with errata
RHSA-2005:0117.


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