Project

General

Profile

Actions
Copy link

Bug #3731

closed

Use cron.d instead of the crontab to store Rudder cron entry (also in initial promises)

Added by Jonathan CLARKE over 11 years ago. Updated over 11 years ago.

Status:
Released
Priority:
2
Assignee:
Nicolas CHARLES
Category:
System techniques
Target version:
2.5.5
Pull Request:
https://github.com/Normation/rudder-t...
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.

Related issues 1 (0 open — 1 closed)

Related to Rudder - User story #3190: Use cron.d instead of the crontab to store Rudder cron entryReleasedNicolas CHARLES2013-01-14Actions
Actions
Copy link

Also available in: Atom PDF