diff options
| author | russell <russell@f38db490-d61c-443f-a65b-d21fe96a405b> | 2008-12-09 22:17:39 +0000 |
|---|---|---|
| committer | russell <russell@f38db490-d61c-443f-a65b-d21fe96a405b> | 2008-12-09 22:17:39 +0000 |
| commit | 9269b46da804da1972fd15ec830b79e43d34b12f (patch) | |
| tree | f5d3c6c088ab2170c9ab2218ba589007a7a9729f /main/asterisk.c | |
| parent | 8fac3e83341e89faa77912bff43f002319f1c901 (diff) | |
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.4@162413 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'main/asterisk.c')
| -rw-r--r-- | main/asterisk.c | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/main/asterisk.c b/main/asterisk.c index d0f6e487b..230f9c830 100644 --- a/main/asterisk.c +++ b/main/asterisk.c @@ -2981,10 +2981,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_makesocket(); sigemptyset(&sigs); sigaddset(&sigs, SIGHUP); |