-
-
Notifications
You must be signed in to change notification settings - Fork 54
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
Question about OS-default configurations #193
Comments
Replying to this old comment to confirm, for anyone else confused by this (like me): this module does indeed not provide any default configuration. Nothing generic and nothing OS-specific. It will, however, delete any default configuration that was put in place by the package manager and leave you with a non-functioning, unable-to-start rsyslog service. Nothing in the README indicates this would be the case. On the contrary, the README explicitly states that just doing So to people new to this module (if any): be sure to define the rsyslog configuration you expect before deploying this module, and maybe turn off purging of config files. |
Just got bit by this when trying to migrate from @saz's module to this one. This is some serious Neckbeard stuff. Rsyslog is hard enough to grok, outright removing sane defaults is pretty horrible behavior. |
@peelman that is your opinion. IMHO it is actually a good thing, most defaults that I have seen so far don't do at all what I want. But as usual merge requests are always welcome :) |
Have you tried submitting a merge request to the rsyslog folks with your preferred defaults that may be more useful? This statement is in fact, a lie. It does quite the opposite. |
Just a clarification for me here.
Do I see this correctly, that the module does not include the OS' default configuration that you'd get when you just install rsyslog? I see that /etc/rsyslog.conf and /etc/rsyslog.d is replaced (if you not set purge_config_files to false), but the configuration from these files isn't prevailed.
So if we'd want to use the module on our network, we'd have to include all the defaults for the different OSes we're managing ourselves, right?
The text was updated successfully, but these errors were encountered: