aboutsummaryrefslogtreecommitdiffstats
path: root/config.sub
diff options
context:
space:
mode:
authordvossel <dvossel@f38db490-d61c-443f-a65b-d21fe96a405b>2009-06-17 19:54:01 +0000
committerdvossel <dvossel@f38db490-d61c-443f-a65b-d21fe96a405b>2009-06-17 19:54:01 +0000
commit8571f05a78ad591b2a3ce68db14e796fded9c864 (patch)
tree87a09d5a7e91a393635159ac07dbd29f7977a63a /config.sub
parent5715fd3810e8c639996b0e6adec0ea2d078f6c1e (diff)
Merged revisions 201445 via svnmerge from
https://origsvn.digium.com/svn/asterisk/trunk ................ r201445 | dvossel | 2009-06-17 14:45:35 -0500 (Wed, 17 Jun 2009) | 25 lines Merged revisions 201423 via svnmerge from https://origsvn.digium.com/svn/asterisk/branches/1.4 ........ r201423 | dvossel | 2009-06-17 14:28:12 -0500 (Wed, 17 Jun 2009) | 19 lines StopMixMonitor race condition (not giving up file immediately) StopMixMonitor only indicates to the MixMonitor thread to stop writing to the file. It does not guarantee that the recording's file handle is available to the dialplan immediately after execution. This results in a race condition. To resolve this, the filestream pointer is placed in a datastore on the channel. When StopMixMonitor is called, the datastore is retrieved from the channel and the filestream is closed immediately before returning to the dialplan. Documentation indicating the use of StopMixMonitor to free files has been updated as well. (closes issue #15259) Reported by: travisghansen Tested by: dvossel Review: https://reviewboard.asterisk.org/r/283/ ........ ................ git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.6.1@201448 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'config.sub')
0 files changed, 0 insertions, 0 deletions