Isn't it a problem with your instantiate script that it does not cater for a stale PID file? Seems like the lsb function start_daemon takes care of this since the AMF sample program uses it and there is no problem there. Not that an SA-aware component is supposed to do exit() in context of the terminate callback. /Hans
From: opensaf dev [mailto:[email protected]] Sent: den 12 augusti 2013 09:08 To: Hans Feldt Cc: [email protected] Subject: Re: [users] clean up not called while locking SU Hi Hans, Since unlock-in creates the process, I was expecting lock-in should have terminated the process, resources like pid file etc. How to terminate all the sa-aware components running normally in an SU with clearing all the pid file and process in OpenSAF? In this case components have not reported any error to the framework, its a normal scenario. Are there any other admin commands or IMM configurations for the SU to do so? Thanks, Dev On Sun, Aug 11, 2013 at 11:39 PM, Hans Feldt <[email protected]<mailto:[email protected]>> wrote: Again cleanup command is only called where there is component error. Not when lock-in is issued. /Hans On 08/09/2013 04:00 AM, opensaf dev wrote: Could somebody look at the issue I am facing, on the cleanup not being called while locking in a SU. Thanks, Dev ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ Opensaf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-users
