After that, you'll start getting "to many files open" messages (on a vanilla system install) and the server will go temporarily unresponsive (which can be semi-remedied by modifying your OS's max open files - but even then * had problems).
On Oct 18, 2004, at 5:11 PM, Matt G wrote:
Hi All,
I have a quick question regarding restarting (and/or stopping/restarting) asterisk daily -- Should it be done?
I've seen conflicting answers, some people have told me that the only reason for asterisk to be stopped/started daily was for mpg123 causing many childs, which has since been fixed using 'no buffer' or 'nb' appended to the line in musiconhold.conf.
Others have told me there is no reason whatsoever to restart/stop it, yet there's instructions on how to do it on the wiki, are these just outdated?
Is there any other reason why one would want to stop and restart asterisk daily? (or at any other scheduled time?)
On a related note, is asterisk -rx "restart now" the equivalent of asterisk -rx "stop now" && /usr/sbin/safe_asterisk (or whatever command is used to restart it)?. I have a job cronned on a slackware system to restart it daily using -rx "restart now" and it creates a new PID, and Process Time, but when I run the same thing on Redhat 9 I get an error saying that it exited on sig 13. I'm sure this is just a redhat specific thing as this isn't the only problem I'm running into, but it would be nice to find some answers.
Thanks, Matt
_______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
