defaultLinuxLogsLocation not applied to start-rpm-template #675
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.
Where an application is installed using an RPM and the defaultLinuxLogsLocation is set the rpm would correctly create the logging folders for the application at the new location. Unfortunately the daemon would still try to log in the default location which was hard coded which resulted in the daemon failing.
This change removes the hard coding from the logging in the start-rpm-template to instead use the value which originates from the LinuxPlugin. If the value is overridden the daemon will now log to the specified location.
An RPM built with those changes was run on a centos 6.7 machine and the universal/* and rpm/* tests were all run successfully