On Wed, Nov 07, 2007 at 07:16:48AM -0500, J. Oquendo wrote:
> Per Jessen wrote:
> > Andrea Spadaccini wrote:
> >
> >> IMHO it's better to build a FSM (Finite State Machine) that handles
> >> the Asterisk process and other collateral processes (like the MAPI
> >> proxy) and let it monitor the process.
> >>
> >> Moreover, you should make this FSM sensible to UNIX signals in order
> >> to start, stop, restart Asterisk easily if you want.
> >
> > Hi Andrea
> >
> > that's exactly the kind of elaborate scheme I was hoping to avoid. What
> > do you do today?
> >
> >
> > /Per Jessen, Zürich
> >
>
>
> echo "/bin/ps -C asterisk || { /usr/sbin/asterisk & }" >
> /usr/local/bin/alwaysup
> chmod +x /usr/local/bin/alwaysup
>
> In your crontab:
> */1 * * * * /usr/local/bin/alwaysup >/dev/null 2>&1
That's even worse. I can imagine what happeens if you actually decided
you wanted to stop Asterisk.
--
Tzafrir Cohen
icq#16849755 jabber:[EMAIL PROTECTED]
+972-50-7952406 mailto:[EMAIL PROTECTED]
http://www.xorcom.com iax:[EMAIL PROTECTED]/tzafrir
_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
