Bug #7614
closed
backup files should not be in conf.d folders
Added by Anonymous about 9 years ago.
Updated over 2 years ago.
Description
Hello,
in #7434 the timestamp backup of all edit files bundles was activated. Some programs don't like these backup files in their conf.d folders, like sudo (/etc/sudoers.d/) or apt (/etc/apt/sources.list.d/). They are complaining about files that have the wrong extension or are just accepting a file with options that are no longer valid.
Bye, Ronny
- Related to User story #7434: Add edit-default with backup on all edit files added
- Translation missing: en.field_tag_list set to Quick and important
- Assignee set to Nicolas CHARLES
- Target version set to 0.x
- Status changed from New to In progress
This needs to be defined in the body agent control (not existing in ncf)
We can either add it to the promises.cf file, or mimic the cfengine standart way (the masterfiles have it in controls/cf_agent.cf), so we could have it in 10_ncf_internals/cf_agent.cf
Ok, selected solution is in promiseS.cf, so it won't conflict with either CFEngine Masterfiles own config file, nor Rudder's
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/ncf/pull/308
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Status changed from Pending release to Released
- Target version changed from 0.x to ncf-0.x
- Priority set to 0
- Project changed from 41 to Rudder
- Category set to Generic methods
Also available in: Atom
PDF
Updated by Jonathan CLARKE 
Updated by 
Updated by 
Updated by