On Tue, 8 Feb 2011 14:29:16 -0300, "Ulisses Reina Montenegro de Albuquerque" <ulisses.montene...@cesar.org.br> wrote: >I haven't looked at the Asterisk callback code, but are you sure it uses >polling? Based on the description on the page I'd say it's more likely do be >based on inotify[1], should be enabled for the filesystem type you are >monitoring (I am not sure whether it is available for all FS drivers).
Thanks Ulisses. I'm not much of a developer so don't have enough technical knowledge to tell, but others documents also say that Asterisk checks a specific directory several times per second, hence the need to use mv instead of cp, since mv is atomic. I didn't about about inotify. I'll read up and see if maybe the uClinux/Asterisk this appliance uses or the yaffs filesystem it uses as root filesystem could be the reason for this behavior. http://en.wikipedia.org/wiki/Inotify I did notice something, though, that could shed some light: The callback file is ignored if I just move it to the directory while Asterisk is running. However, if I stop Asterisk, move/copy the file, and then start Asterisk, the callback file is handled. Could this mean anything? Thank you. _______________________________________________ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
