Qingshan Xie wrote: > hello, > we have a 2.0.59 running on Solaris 8. We > configured mod_ssl SSLSessionCache and SSLMutex as > below, > SSLSessionCache > dbm:/opt/httpd/logs/httpd-ssl-443/ssl_scache > SSLSessionCacheTimeout 300 > SSLMutex file:/opt/httpd/logs/httpd-ssl-443/ssl_mutex > > However, we never see the log file, ssl_mutex, > created. Can some one tell me why? I noticed the > logs including ssl_mutex is on a NFS, not a physical > local disk. Would this be the cause? NFS for logs and databases are sub-optimal. For locks, they are generally lethal. If the ssl_scache is not shared, then the ssl_mutex should never be on shared storage. Oh - and the path needs to be writeable by nobody and root for the cache and mutex to both be created, and updated. The cache file is not held open, but is reopened for each update while the worker processes are running as your configured User (usually 'nobody'). Bill --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|