rpm: Fix installation path of SysV startup script #23
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Do not use /etc/init.d for SysV init scripts for RPM-based linux distros. The directory should be /etc/rc.d/init.d. When using /etc/init.d and no chkconfig or initscripts packages are installed first, this package was creating /etc/init.d as a directory. Unfortunately, if you wanted to later install a package that brought in the chkconfig package, the RPM transaction would fail because it assumes it can create a symlink in /etc/init.d when a directory already exists. A bug was filed for this here: osquery/osquery#7949
jbillingredhat
requested review from
alessandrogario,
theopolis,
muffins,
Smjert,
directionless and
zwass
as code owners
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Do not use /etc/init.d for SysV init scripts for RPM-based linux distros. The directory should be /etc/rc.d/init.d.
When using /etc/init.d and no chkconfig or initscripts packages are installed first, this package was creating /etc/init.d as a directory. Unfortunately, if you wanted to later install a package that brought in the chkconfig package, the RPM transaction would fail because it assumes it can create a symlink in /etc/init.d when a directory already exists.
A bug was filed for this here:
osquery/osquery#7949