I've actually had an AGI script that Asterisk never closed the fork for. It was testing a particular feature so it was pretty badly written. Ended up consuming a lot of resources.
No idea why Asterisk hated that script, though. Failed to kill it every time. But would continue on the dial plan after I sent back the data it needed and supposedly ended the program. Never had it happen since On Jan 12, 2013 12:56 PM, "Steve Edwards" <[email protected]> wrote: > On Sat, 12 Jan 2013, Stelios Koroneos wrote: > > The biggest issue i have faced in term of stability is badly written AGI >> scripts that tend to hog resources and bring systems down in the end. >> > > Veering off topic, but still curious :) > > Since an AGI only exists for part of the life of a single call, how does > it accumulate enough resources to be a problem? > > -- > Thanks in advance, > ------------------------------**------------------------------** > ------------- > Steve Edwards [email protected] Voice: +1-760-468-3867 PST > Newline Fax: +1-760-731-3000 > > -- > ______________________________**______________________________**_________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > > http://lists.digium.com/**mailman/listinfo/asterisk-**users<http://lists.digium.com/mailman/listinfo/asterisk-users> >
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
