Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1358804 - cronie has a bug when run with syslog flag
Summary: cronie has a bug when run with syslog flag
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: cronie
Version: 6.7
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Tomas Mraz
QA Contact: Jakub Prokes
URL:
Whiteboard:
Depends On: 1237093
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-21 14:00 UTC by Jan Kurik
Modified: 2016-08-23 18:39 UTC (History)
10 users (show)

Fixed In Version: cronie-1.4.4-16.el6_8.2
Doc Type: Bug Fix
Doc Text:
Previously, when cronie was set to redirect cronjob output to syslog using the "-s" flag, the output loop exited prematurely. Consequently, the output was truncated after the first character. With this update, the output loop no longer exits prematurely. As a result, cronjob output is logged correctly now.
Clone Of: 1237093
Environment:
Last Closed: 2016-08-23 18:39:29 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1667 normal SHIPPED_LIVE cronie bug fix update 2016-08-23 22:35:16 UTC

Description Jan Kurik 2016-07-21 14:00:30 UTC
This bug has been copied from bug #1237093 and has been proposed
to be backported to 6.8 z-stream (EUS).

Comment 7 errata-xmlrpc 2016-08-23 18:39:29 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-1667.html


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