[OpenSER-Devel] [ openser-Bugs-1725043 ] cleanup() not called when openser is killed

SourceForge.net noreply at sourceforge.net
Tue Nov 13 18:18:20 UTC 2007


Bugs item #1725043, was opened at 2007-05-24 19:53
Message generated for change (Comment added) made by bogdan_iancu
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1725043&group_id=139143

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: core
Group: ver 1.2.x
>Status: Closed
>Resolution: Invalid
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Bogdan (bogdan_iancu)
Summary: cleanup() not called when openser is killed

Initial Comment:
Hi,

When the main process receive a SIGKILL (or SIGINT) signal it call kill_all_children(SIGTERM) but it never returns from this function. So, it never calls cleanup(1) and the destroy_function() of each module is never call. 

But, when I kill a child the main process receives a SIGCHLD signal and, in this case, every thing works normally: The destroy_function of each module is call. This situation gives a chance to (my) module to close files, network sessions and kill its own child.

Tested on SunOS 5.8 and 5.10 with openser 1.2.0

-- blogarithme

----------------------------------------------------------------------

>Comment By: Bogdan (bogdan_iancu)
Date: 2007-11-13 20:18

Message:
Logged In: YES 
user_id=1275325
Originator: NO

Hi,

Based on the tests I run (following your report), I was not able to
reproduce this behaviour at all. 

The kill_all_children() cannot block as it only sends signal by using
kill(), which is a not blocking operation.

I suspect the problem is somewhere else located (like this is side efect
of another bug). If you can still reproduce this, try to get more on this
(gdb inspection, CPU consumtion, etc) and open a new report.

regards,
Bogdan

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1725043&group_id=139143



More information about the Devel mailing list