Bug #4155
closed
Commands to check and restart cron daemon on Fedora are not correct
Added by Christophe Nowicki about 11 years ago.
Updated over 10 years ago.
Category:
System techniques
Description
Hi,
Fedora is using SystemD and other GNU/Linux distributions are adopting this init system.
Could you fix the check_cron_daemon in :
https://github.com/Normation/rudder-techniques/blob/master/initial-promises/node-server/promises.cf
Current version is :
vars:
redhat::
"cron_bin" string => "crond$";
"cron_restartcmd" string => "/etc/init.d/crond restart";
ubuntu::
"cron_bin" string => "cron$";
"cron_restartcmd" string => "/etc/init.d/cron restart";
!(redhat|ubuntu)::
"cron_bin" string => "/usr/sbin/cron$";
"cron_restartcmd" string => "/etc/init.d/cron restart";
Could you add fedora and use service instead of '/etc/init.d/*'
vars:
redhat::
"cron_bin" string => "crond$";
"cron_restartcmd" string => "/etc/init.d/crond restart";
fedora::
"cron_bin" string => "crond$";
"cron_restartcmd" string => "/bin/systemctl restart crond.service"";
ubuntu::
"cron_bin" string => "cron$";
"cron_restartcmd" string => "/etc/init.d/cron restart";
!(redhat|ubuntu|fedora)::
"cron_bin" string => "/usr/sbin/cron$";
"cron_restartcmd" string => "service cron restart";
Best Regards,
- Assignee set to Matthieu CERDA
Thanks for reporting!
Matthieu, I believe you're the one for that one.
- Category set to System techniques
- Status changed from New to In progress
- Priority changed from N/A to 2
- Target version set to 2.9.3
- Target version changed from 2.9.3 to 2.6.11
- Status changed from In progress to Pending technical review
- Assignee changed from Matthieu CERDA to Jonathan CLARKE
- % Done changed from 0 to 100
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/277
- Status changed from Pending technical review to Pending release
Applied in changeset policy-templates:commit:0a15d6ba5ad447e807670b59faef062d1f46ecf0.
Applied in changeset policy-templates:commit:397f69218c8ed2ce6ba8225e1299deba8447538d.
Thanks for this, it has been merged.
However, it made me realise that the fix for #4156 is wrong - it uses hard class "Fedora" instead of "fedora", so won't work. I'll reopen and assign to you, Matthieu.
- Status changed from Pending release to 8
- Assignee changed from Jonathan CLARKE to Matthieu CERDA
While reviewing the fix for #4155, I realised that the fix committed here won't work: it uses hard class "Fedora" instead of "fedora", so won't work.
Reopening. Matthieu, please adjust this.
- Status changed from 8 to Pending technical review
Jonathan CLARKE wrote:
While reviewing the fix for #4155, I realised that the fix committed here won't work: it uses hard class "Fedora" instead of "fedora", so won't work.
Reopening. Matthieu, please adjust this.
Whoops, I reopened the wrong ticket. Closing again, sorry for the noise.
- Status changed from Pending technical review to Pending release
- Subject changed from check_cron_daemon on Fedora to Commands to check and restart cron daemon on Fedora are not correct
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.6.11, which was released today.
Check out:
- Related to Bug #6566: promises.cf's "bundle agent check_cron_daemon" is not systemd aware added
- Related to Bug #6735: cronConfiguration is not compatible with RHEL 7 and SLES 12 added
- Related to deleted (Bug #6735: cronConfiguration is not compatible with RHEL 7 and SLES 12)
Also available in: Atom
PDF