-
Notifications
You must be signed in to change notification settings - Fork 229
systemd: used drop-ins for configuration #829
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| [Manager] | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -519,6 +519,9 @@ fi | |
| %config(noreplace) %{_sysconfdir}/tuned/tuned-main.conf | ||
| %config(noreplace) %verify(not size mtime md5) %{_sysconfdir}/tuned/bootcmdline | ||
| %verify(not size mtime md5) %{_sysconfdir}/modprobe.d/tuned.conf | ||
| # https://bugzilla.redhat.com/show_bug.cgi?id=2444143 | ||
| %dir %{_sysconfdir}/systemd/system.conf.d | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Assuming this will be there until the systemd package actually starts to provide the system.conf.d directory?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, I hope they will add it. If not, we can keep it. Even in case they add it and we forget to drop it, it will be still according to the Fedora packaging guidelines, because co-ownership of directories is allowed. |
||
| %verify(not size mtime md5) %{_sysconfdir}/systemd/system.conf.d/00-tuned.conf | ||
| %{_tmpfilesdir}/tuned.conf | ||
| %{_unitdir}/tuned.service | ||
| %dir %{_localstatedir}/log/tuned | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wouldn't this file be completely unnecessary after the change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, I guess it's still useful to have it there so that it is removed together with the whole package and wouldn't leave a random configuration file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it's always better to have the package manager to handle it - it will also backup the file in case user already has there his own configuration file with the same name.
The code in the plugin is just a fallback for special cases when the template file is not installed by RPM or
make install, e.g. it could happen on some non RPM distro. IMHO in such case it's better if the plugin works OK and creates the file that could be a leftover later than if it doesn't work.