Bug 475106
Summary: | Updating vixie-cron RPM leaves incorrect SigIgn settings | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Damian Menscher <menscher> |
Component: | vixie-cron | Assignee: | Marcela Mašláňová <mmaslano> |
Status: | CLOSED WONTFIX | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 4.7 | CC: | cjwatson |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-02-22 13:32:43 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
Damian Menscher
2008-12-07 21:19:44 UTC
For this behaviour was responsible makewhatis script, which was fixed two years ago. So what's the problem? The makewhatis script is irrelevant, and was simply one symptom of this bug which was worked around. The real bug is in the rpm install of vixie-cron, which changes the SigIgn settings of the running crond. This bug manifests itself with other scripts that are called by cron. This bug is easy to verify by comparing the SigIgn values before and after an update of the vixie-cron RPM. If you really think it's valid behavior for the SigIgn values to change when crond is restarted by up2date, please document that, as well as workarounds to apply to scripts this breaks. The last planned update of RHEL-4 will be focused on performance and security bugs only. Please reopen in next release if this problem is still valid. Bug #649674 indicates that this is still a problem. I don't know the bug etiquette for reopening this, but it clearly ought to be reopened and put somewhere where it won't be closed just because a Red Hat product went out of support. Please can somebody fix this? I would really prefer not to have to work around this in man-db - it's the wrong place. |