Learn more about these different git repos.
Other Git URLs
See DOMAIN SECTIONS part of the main page. First paragraph is messed up.
I see no problems with the man page formatting.
coverity: => resolution: => worksforme status: new => closed
DOMAIN SECTIONS These configuration options can be present in a domain configuration section, that is, in a section called “[domain/NAME]”.TP min_id,max_id (integer) UID and GID limits for the domain. If a domain contains an entry that is outside these limits, it is ignored. For users, this affects the primary GID limit. The user will not be returned to NSS if either the UID or the primary GID is outside the range. For non-primary group memberships, those that are in range will be reported as expected. Default: 1 for min_id, 0 (no limit) for max_id
Should be
DOMAIN SECTIONS These configuration options can be present in a domain configuration section, that is, in a section called “[domain/NAME]” min_id,max_id (integer) UID and GID limits for the domain. If a domain contains an entry that is outside these limits, it is ignored. For users, this affects the primary GID limit. The user will not be returned to NSS if either the UID or the primary GID is outside the range. For non-primary group memberships, those that are in range will be reported as expected. Default: 1 for min_id, 0 (no limit) for max_id
resolution: worksforme => status: closed => reopened
I see it on RHEL5.5.
Not reproducible on any other system.
resolution: => worksforme status: reopened => closed
Fields changed
rhbz: => 0
Metadata Update from @dpal: - Issue set to the milestone: SSSD 1.5.0
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/1748
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.