Learn more about these different git repos.
Other Git URLs
https://bugzilla.redhat.com/show_bug.cgi?id=874494 (Red Hat Enterprise Linux 6)
Description of problem: It is allowed to set non-numeric values to force_timeout parameter in sssd.conf. Version-Release number of selected component (if applicable): sssd-1.9.2-7.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. Set force_timeout = TRUE in DOMAIN Section of sssd.conf file 2. Restart sssd service. 3. Send SIGSTOP to process sssd_be # kill -s SIGSTOP <PID> 4. Monitor sssd.log file for the messages. # tail -f /var/log/sssd.log Actual results: The sssd service restarts successfully and sssd_be gets killed in 60 secs. Results are similar to the "force_timeout" default behaviour. Expected results: An error should be shown while starting or restarting the sssd service. Non-numeric values shouldn't be allowed while setting force_timeout parameter in sssd.conf.
Fields changed
blockedby: => blocking: => coverity: => design: => design_review: => 0 feature_milestone: => fedora_test_page: => milestone: NEEDS_TRIAGE => SSSD Deferred testsupdated: => 0
blocking: => [https://fedorahosted.org/sssd/ticket/416 416]
Closing as duplicate of #2269
changelog: => mark: => 0 review: => 0 selected: =>
resolution: => duplicate status: new => closed
Metadata Update from @jhrozek: - Issue marked as blocked by: #416 - Issue set to the milestone: SSSD Patches welcome
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/2663
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.