Quoth Gilles Ganault: > 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.
This is true regardless of whether it's polling the directory or using inotify -- it means that it can start to read the file as soon as it is created. > 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. I think this is just more evidence that it's probably using inotify. It'll be doing a single poll on startup (to catch files created while it wasn't listening) and then relying on inotify to tell it about additional files being created so that it doesn't need to poll the directory. _______________________________________________ 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
