This repository has been archived by the owner on Apr 7, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Shall not modify /etc/logrotate #44
Comments
I'm considering using this role for DuckCorp, but there's quite some work to make it working on Debian. I should be able to provide a patch, should you agree on this (that is to say: don't work on it, just give your opinion please). |
The logrotation setting is not a default one, so I think that's minor. And the setting date back to manageiq, on RHEL 6 so I do not have context on why we would want that. I would be in favor of removing it all together, and let people configure logging outside of the role. |
I'm fine with this plan. I can work on this but as said, not on the current master. |
duck-rh
added a commit
that referenced
this issue
Oct 10, 2017
duck-rh
added a commit
that referenced
this issue
Oct 10, 2017
This is outside the scope of this role (see #44).
It is fixed in 135cc0b |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
/etc/logrotate.conf
is a global configuration and this has nothing to do with configuring Apache Httpd and related vhosts or web services. We should strive to respect roles' perimeters./etc/logrotate.d/httpd
is the right file to modify.The text was updated successfully, but these errors were encountered: