Bug #365
closed
Consumerd can't be killed if unable to connect to the error socket
Added by David Goulet about 12 years ago.
Updated about 12 years ago.
Description
When killing the session daemon, a consumerd, that was unable to connect to the error socket, does not quit.
Related to bug 387 because the metadata thread does not quit if the consumer_thread_sessiond_poll thread dies.
It's related because there is a behavior issue.
- Status changed from Confirmed to Resolved
This is fixed. Unable to reproduce the issue.
If the sessiond thread dies in the consumer daemon, everything goes down as well after every streams has hang up (if any existing). Considering that if the consumer error socket is bad for some reason, the sessiond thread will stop and notifies the other threads as well to gracefully quit.
Also available in: Atom
PDF