httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anthony Howe <ach...@snert.com>
Subject Re: apr_global_mutex_child_init & mod_watch
Date Mon, 08 Sep 2003 10:29:48 GMT
> flock is used on FreeBSD by default...  flock requires that chmod be 
> done on the lock in the child init
> 
> if you look at Apache 2.1-dev, unixd_set_global_mutex_perms() has been 
> changed to handle the chmod() for you

You mean chown() right?  Or do you mean both chmod() and chown()?

> at Apache 2.0.48-dev, you have to do the chmod() on the lock file, like 
> mod_ssl does in that branch

Actually I did chown(), not a chmod() and everything worked on FreeBSD. 
The lockfile was create with 0600 permissions already:

#if defined(__unix__)
     /* Set the lockfile ownership, if it exists. This will eventually be
      * handled by unixd_set_global_mutex_perms() in Apache 2.1 and maybe
      * 2.0.48 (but I won't count on it).
      */
     if (chown(tp->lockfile, unixd_config.user_id, 
unixd_config.group_id) && errno != 0 && errno != ENOENT) {
	ap_log_error(...);

     unixd_set_global_mutex_perms((apr_global_mutex_t *) tp->mutex);
#endif

Next Linux testing...

-- 
Anthony C Howe                                 +33 6 11 89 73 78
http://www.snert.com/       ICQ: 7116561         AIM: Sir Wumpus
"                                                " - Zen thought


Mime
View raw message