Fix for combination of MSSQL driver and autofs filesystem for /home #995
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
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.
Make sure systemd has a valid
$HOMEfor Apache.Changes
Makes sure
$HOMEis set to a valid directory when runningsystemctl (re)start httpd. Without this, it appears that$HOMEis set to/homeby systemd. In most circumstances this has no impact, but when using the Microsoft SQL Server driver for PHP (aka SQLSRV) AND if autofs is used to manage users' home directories then a conflict can occur. SQLSRV will then look for the systemd user'sodbcinst.inifile in/home/.odbcinst.ini, and because it doesn't existautofswill attempt to mount it. Depending on autofs settings, this could lead to a very long lag (~2 minutes in one case). This autofs lag can causesystemctl (re)start httpdto timeout.Issues
Post-merge actions
None