(it might be worth mentioning, for anyone encountering an issue like this, that the WAV files asterisk defaults to writing, will not be valid if they grow over 2GB, because it uses 32bit values internally). Basically I suspect there are corner cases here where Asterisk isn't going to handle SIGXFSZ sanely, but I don't have the time/knowledge to find them. Right now the only place in its code which handles that signal is the logging module.
-- Asterisk goes into a catastrophic log rotation loop when a conference recording hits max file size https://bugs.launchpad.net/bugs/249443 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
