On Wed, Oct 28, 2009 at 1:56 PM, Carolyn Beeton <[email protected]> wrote:

>  have you tested this change?  I don't think the supervisor will like
> it... after 10 seconds the sipxopenfire.sh script will exit and the
> supervisor will think openfire has failed.
>

Yes I tested it. He is happy.

The recorded PID is that of the java process.



> Carolyn
>
>  ------------------------------
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *
> [email protected]
> *Sent:* Wednesday, October 28, 2009 1:49 PM
> *To:* [email protected]
> *Subject:* sipXecs 17018 mranga: XX-6892: Openfire PID not written to the
> rightfile.
>
>   Project sipXecs New Revision 
> 17018<http://code.sipfoundry.org//changelog/sipXecs/?cs=17018>
> Committer mranga Date 2009-10-28 12:48:30 -0500 (Wed, 28 Oct 2009) Log
>
>  XX-6892: Openfire PID not written to the right file.
>
>
>
> Modified:
>
>    - main/sipXopenfire/sipxopenfire.sh.in
>    
> <http://code.sipfoundry.org//browse/sipXecs/main/sipXopenfire/sipxopenfire.sh.in?r1=17017&r2=17018>
>
>
> _______________________________________________
> sipx-dev mailing list [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-dev
> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
> sipXecs IP PBX -- http://www.sipfoundry.org/
>



-- 
M. Ranganathan
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to