http://bugzilla.lysator.liu.se/show_bug.cgi?id=1403
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |2.1.3
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=1403
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Keywords| |inpro
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=1403
Summary: lyskomd crashes with "failed to re-enable session"
Product: lyskomd
Version: 2.1.2
Platform: All
OS/Version: All
Status: NEW
Severity: critical
Priority: P1
Component: server
AssignedTo: ceder(a)lysator.liu.se
ReportedBy: ceder(a)lysator.liu.se
QAContact: lyskomd-qa(a)lists.lysator.liu.se
If a disabled session tries to sends output to a client, and gets an error,
the state of that session will be set to ISC_STATE_CLOSING. The attempt
by check_idle_callback() to re-enable the session will fail, and lyskomd
will call restart_kom("failed to re-enable session\n"). This will result
in loss of data.
LysLysKOM has been using the attached patch more than four months, and no more
crashes have occured. However, I'm not sure it doesn't introduce a small
memory leak. A test case is needed.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.