add configuration variables for pam_limits #317
Merged
Conversation
This file contains hidden or 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
bartowl
force-pushed
the
fix/pam_limits_config
branch
2 times, most recently
from
b52104c to
bca6bcd
Compare
bartowl
force-pushed
the
fix/pam_limits_config
branch
from
bca6bcd to
b592da7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR adds possibility to switch on/off the configuration of pam.d entry in pam.d/login and security.d/limits.d/99-oracle-limits.conf for oracle user. It was currently only possible to exclude this by using skip_tags, now it should be possible also via inventory.