Match what we do with the ssl_scache_dbm

chown junk, which we know is safe and works, and more directly
handles the issue with chown (agreed that a macro is needed
eventually)

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@99148 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/modules/ssl/ssl_engine_mutex.c b/modules/ssl/ssl_engine_mutex.c
index ae4e3c464300f0c0bd542d63e7123ebea639f400..ad029b02d7f10c63a744d04a28b7a8f23b181a91 100644 (file)
--- a/modules/ssl/ssl_engine_mutex.c
+++ b/modules/ssl/ssl_engine_mutex.c
@@ -88,7 +88,7 @@ int ssl_mutex_init(server_rec *s, apr_pool_t *p)
                          "Cannot create SSLMutex");
         return FALSE;
     }
-#if APR_HAS_FLOCK_SERIALIZE
+#if !defined(OS2) && !defined(WIN32) && !defined(BEOS) && !defined(NETWARE)
     if (mc->szMutexFile && mc->ChownMutexFile == TRUE)
         chown(mc->szMutexFile, unixd_config.user_id, -1);
 #endif