Description of problem: If you try to start SSSD services with an invalid sssd.conf file - example: no domains configured. The service appears to start successfully and returns 0. [root@localhost sssd]# service sssd start Starting sssd: [ OK ] [root@localhost sssd]# echo $? 0 [root@localhost sssd]# service sssd status sssd dead but pid file exists [root@localhost sssd]# ps -ef | grep sssd root 11646 11544 0 11:36 pts/0 00:00:00 grep sssd This is true for both Fedora 11 and RHEL 5.3. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. yum install sssd 2. do not edit sssd.conf file, but use default with no domains configured and start SSSD service sssd start 3. echo $? 4. service sssd status 5. ps -ef | grep sssd Actual results: Service appears to start successfully return code status is 0 pid file is created even service did not start Expected results: Appropriate error message non 0 return code status pid file not created Additional info:
bug also logged against F11 - bug #512733
closing as duplicate *** This bug has been marked as a duplicate of bug 512733 ***