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
--
====================================================
J. Oquendo
SGFA (FW+VPN v4.1)
SGFE (FW+VPN v4.1)
"I hear much of people's calling out to punish the
guilty, but very few are concerned to clear the
innocent." Daniel Defoe
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xF684C42E
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ --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
