More notes on the ircd zombie session problem
This commit is contained in:
parent
a4ae0ae270
commit
6703c5ef9a
|
@ -7,3 +7,11 @@ teardown of the previous connection; so the new session-listener
|
||||||
responds to the assertions from the old connection before the old
|
responds to the assertions from the old connection before the old
|
||||||
connection has a chance to die. Of course, it *does* die (since commit
|
connection has a chance to die. Of course, it *does* die (since commit
|
||||||
11de40c), but having that zombie reborn new session is annoying.
|
11de40c), but having that zombie reborn new session is annoying.
|
||||||
|
|
||||||
|
- This is thorny. You'd think that having a session wait for its
|
||||||
|
line-reader to go would be enough, but the multiple nested
|
||||||
|
during/spawns creating the sessions mean that no matter how long
|
||||||
|
the old session instance sticks around, a new session will appear
|
||||||
|
before we're ready! ... maybe there's no way *at all* to
|
||||||
|
disambiguate old/new instances without, say, a unique
|
||||||
|
listener-socket identifier??
|
||||||
|
|
Loading…
Reference in New Issue