Actions
Bug #3731
closed
Use cron.d instead of the crontab to store Rudder cron entry (also in initial promises)
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
In Rudder 2.5.0, via ticket #3190, we moved the cron entry that checks Rudder's agent (cf-execd) is running from /etc/crontab to a dedicated file, /etc/cron.d/rudder-community.
However, this change was never put in the initial promises, so on first installation of rudder-agent, it would still edit /etc/crontab.
Fixing.
Updated by Jonathan CLARKE almost 11 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Jonathan CLARKE to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/150
PR available in https://github.com/Normation/rudder-techniques/pull/150
Updated by Jonathan CLARKE almost 11 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset policy-templates:commit:f2c9c7382d445c96582c6398c11d94d73c066d84.
Updated by Nicolas CHARLES almost 11 years ago
Applied in changeset policy-templates:commit:9b9e9e5ecb013b137bd35d330b6617a46f47a3ed.
Updated by Nicolas PERRON over 10 years ago
- Status changed from Pending release to Released
Updated by Nicolas PERRON over 10 years ago
This bug has been fixed in Rudder 2.5.5, which was released today.
Check out:
- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2013-July/000040.html
- The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog25
- Download information: http://www.rudder-project.org/foswiki/Download/
Actions