Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Role does not provide a way to avoid duplicate entries #27

Closed
colin-nolan opened this issue May 3, 2017 · 1 comment
Closed

Role does not provide a way to avoid duplicate entries #27

colin-nolan opened this issue May 3, 2017 · 1 comment

Comments

@colin-nolan
Copy link

A number of logrotate configurations come pre-defined in /etc/logrotate.d/. If this role is used to define the configuration for a path that is already configured, logrotate reports:

error: <basename(path)>:3 duplicate log entry for <path>

and then it looks like it gives precedence to the configuration defined in the file with the name of the lowest lowest lexicographic ordering.

It would be good if there was a way of removing any other other configurations to ensure that that set by this role gets run.

colin-nolan pushed a commit to wtsi-hgi/ansible-logrotate that referenced this issue May 8, 2017
colin-nolan pushed a commit to wtsi-hgi/ansible-logrotate that referenced this issue May 8, 2017
@nickhammond
Copy link
Owner

Removing files should be done with the Ansible file module with a state of absent, this role and most roles should not be destructive in their operations.

colin-nolan pushed a commit to wtsi-hgi/ansible-logrotate that referenced this issue Apr 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants