Bug 711654
Summary: | crontab PATH not properly expanded | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | JW <ohtmvyyn> |
Component: | cronie | Assignee: | Marcela Mašláňová <mmaslano> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | mmaslano, pertusus, tmraz |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-09-04 11:36:13 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
JW
2011-06-08 04:43:46 UTC
This is really nontrivial. To fully emulate the shell expansion the shell would have to be called to expand the right hand side of the env assignment. Of course this expansion would have to run as the appropriate crontab user and with the environment same as it would be seen by the user session. Having the cronie to do some trivial expansion on itself would mean that it would not be fully shell compatible anyway. I beg to differ. This IS relatively trivial. I've written similar code and it comes to now more than 200 lines of code (and I use braces on separate lines!).
> Having the cronie to do some trivial expansion on itself would mean that it
> would not be fully shell compatible anyway.
But wait - first you say it would be "nontrivial", now in almost the same breath you say "trivial".
And saying that "cronie" would somehow not be fully shell compatible is a nonsense. We are only talking about the expansion of the rhs on a minor number of lines of a crontab - only the env lines and they are already treated separately from other lines.
In what way would cronie not be "fully shell compatible"? Please explain.
And I also suggest you read the code first.
Patches are of course welcome :) No change in last three years. Closing. |