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

Fixes #6842: Edit only one syslog configuration at a time #705

Conversation

Kegeruneku
Copy link

@peckpeck
Copy link
Member

What if someone has an old configuration file that is not used because they have migrated from a daemon to another one ?

@Kegeruneku
Copy link
Author

That's precisely the case I'm trying to solve: we want only one active configuration. rsyslog is becoming the de-facto standard, that's why I give it the top priority. Do you think I should use another indicator instead ?

@Kegeruneku Kegeruneku closed this Jun 26, 2015
@Kegeruneku Kegeruneku reopened this Jun 26, 2015
@peckpeck
Copy link
Member

I think there is no problem at all. Testing the existence of a file is almost free whereas you don't know the reason a user may have to change his syslog daemon. He can go from rsyslog to syslog-ng if he needs a new feature.
So I don't see any gain in doing this.

@peckpeck peckpeck closed this Jun 29, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants