On Sat, Jun 17, 2006 at 09:31:54PM -0500, Aaron Daniel wrote: > On Sat, 17 Jun 2006, Douglas Garstang wrote: > > >Other applications can handle it. Don't see why Asterisk can't. Mount the > >nfs volume with the -soft option. Do a 'df -k' and you will see that the > >df command will time out in a couple of seconds. Why can't Asterisk do the > >same? > > Just gonna throw gas on the fire. df -h doesn't continuously poll the > drive for data, asterisk is (for mwi). So each timeout turns into another > timeout. Didn't you already test changing the time on checkmwi? And did > it not change the behavior (not necessarily for the better)?
Your theory is easy to check with watching the state of the main asterisk thread, or maybe strace -p MAIN_ASTERISK_PID . If it remains hung constantly in a D state on the same system call, a shorter timeout just wouldn't have helped. -- Tzafrir Cohen sip:[EMAIL PROTECTED] icq#16849755 iax:[EMAIL PROTECTED] +972-50-7952406 [EMAIL PROTECTED] http://www.xorcom.com _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
