summaryrefslogtreecommitdiff
path: root/server/responder/pam
diff options
context:
space:
mode:
authorSimo Sorce <ssorce@redhat.com>2009-03-11 16:16:20 -0400
committerSimo Sorce <ssorce@redhat.com>2009-03-11 16:26:58 -0400
commit97bc7d0cb0c5fa245b2736d51295d1da0d8311e0 (patch)
treebb645223576fec1edc21b3f139deac5f34b3f028 /server/responder/pam
parent22ff503ab1a8b8fb76f759048e64c621e7560b31 (diff)
downloadsssd-97bc7d0cb0c5fa245b2736d51295d1da0d8311e0.tar.gz
sssd-97bc7d0cb0c5fa245b2736d51295d1da0d8311e0.tar.bz2
sssd-97bc7d0cb0c5fa245b2736d51295d1da0d8311e0.zip
Fix calling setsid and resolve the sssd signal bug
For some reason we were not testing for HAVE_SETSID in configure therefore the setsid() function was never called. This failed to set the process group after the first fork. Remove ifdef because we depend on setsid() anyway, so if it is not available on some platform it is better to fail rather then silently succeed but not have the right process group set up.
Diffstat (limited to 'server/responder/pam')
0 files changed, 0 insertions, 0 deletions