Perform extra checks before attempting to close our socket after a fork

[sssd-bot]

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/790

• Created at 2011-02-07 15:49:16 by simo
• Closed as Fixed
• Assigned to simo
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=670511

---

See https://bugzilla.redhat.com/show_bug.cgi?id=670511 for an example application that does strange stuff and may cause us to close the wrong file descriptor.

Add extra code to be sure we are going to close only our own socket after a fork.

Comments

---

Comment from simo at 2011-02-07 15:52:39

attachment
0001-Check-that-the-socket-is-really-ours-before-attempti.patch

---

Comment from simo at 2011-02-07 15:53:10

Fields changed

status: new => assigned

---

Comment from sgallagh at 2011-02-08 14:58:50

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.5.2

---

Comment from sgallagh at 2011-02-08 15:00:21

Fixed by b005a24

resolution: => fixed
status: assigned => closed

---

Comment from mkosek at 2011-12-16 15:58:38

Fields changed

rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=670511 670511]

---

Comment from simo at 2017-02-24 14:27:47

Metadata Update from @Simo:

• Issue assigned to simo
• Issue set to the milestone: SSSD 1.5.2