aboutsummaryrefslogtreecommitdiffstats
path: root/main/asterisk.c
diff options
context:
space:
mode:
authorrussell <russell@f38db490-d61c-443f-a65b-d21fe96a405b>2008-12-09 22:30:52 +0000
committerrussell <russell@f38db490-d61c-443f-a65b-d21fe96a405b>2008-12-09 22:30:52 +0000
commit96465e7d59363b68d0a86473510c9431610fd827 (patch)
tree218726ba970bbec099f6565ccc5ecabbd59c0f21 /main/asterisk.c
parent8d0bd39ed2834f7b33e1697323fc0b177463137d (diff)
Merged revisions 162414 via svnmerge from
https://origsvn.digium.com/svn/asterisk/trunk ................ r162414 | russell | 2008-12-09 16:25:06 -0600 (Tue, 09 Dec 2008) | 16 lines Merged revisions 162413 via svnmerge from https://origsvn.digium.com/svn/asterisk/branches/1.4 ........ r162413 | russell | 2008-12-09 16:17:39 -0600 (Tue, 09 Dec 2008) | 8 lines Remove the test_for_thread_safety() function completely. The test is not valid. Besides, if we actually suspected that recursive mutexes were not working, we would get a ton of LOG_ERROR messages when DEBUG_THREADS is turned on. (inspired by a discussion on the asterisk-dev list) ........ ................ git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.6.0@162415 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'main/asterisk.c')
-rw-r--r--main/asterisk.c4
1 files changed, 0 insertions, 4 deletions
diff --git a/main/asterisk.c b/main/asterisk.c
index b8a95064d..991e9f98a 100644
--- a/main/asterisk.c
+++ b/main/asterisk.c
@@ -3264,10 +3264,6 @@ int main(int argc, char *argv[])
}
#endif
- /* Test recursive mutex locking. */
- if (test_for_thread_safety())
- ast_verbose("Warning! Asterisk is not thread safe.\n");
-
ast_event_init();
ast_makesocket();