Hi Brett,
no, there is no timeout for the lock. so, if you are not careful in
releasing the lock, you are a dead man with a dead opensips :).
We plan to add some mechanism to check and cleanup locks after the route
is ended, but this requires some extra work in the core part (some
callbacks to give access to executing any kind of route).
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 11/28/2012 06:55 PM, Brett Nemeroff wrote:
Liviu,
This is a good idea. What happens to the child process as it's waiting
for a lock to be released? Are there any protections against locks
lasting indefinitely?
Thanks,
Brett
On Wed, Nov 28, 2012 at 9:02 AM, Liviu Chircu <[email protected]
<mailto:[email protected]>> wrote:
The cfgutils module now provides the possibility of defining atomic
test-and-set operations in the OpenSIPS script.
Such need is a result of complex mixing in script of various
functionality / functions from different modules. Like testing
is done based on ratelimit module and the setting is done in
dialog module.
Modules do provide internal locking and synchronization for their
own functionalities, but cannot cover a more complex and various
scenarios of test-and-set scripting scenarios.
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
