Project

General

Profile

Actions

Bug #3731

closed

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

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

Status:
Released
Priority:
2
Category:
System techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
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 open1 closed)

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

Updated by Jonathan CLARKE over 9 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
Actions #2

Updated by Jonathan CLARKE over 9 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

Applied in changeset policy-templates:commit:f2c9c7382d445c96582c6398c11d94d73c066d84.

Actions #3

Updated by Nicolas CHARLES over 9 years ago

Applied in changeset policy-templates:commit:9b9e9e5ecb013b137bd35d330b6617a46f47a3ed.

Actions #4

Updated by Nicolas PERRON over 9 years ago

  • Status changed from Pending release to Released
Actions #5

Updated by Nicolas PERRON over 9 years ago

This bug has been fixed in Rudder 2.5.5, which was released today.
Check out:

Actions

Also available in: Atom PDF