On Aug 15, 2011, at 1:45 PM, Simone Caruso wrote:
On 15/08/2011 01:44, Nick Kew wrote:
or set up something server-wide
How? there's some code that can i read?
You can use a global variable which gets set during apache's startup, you have
to treat it as read only after the childs
I am trying to implement an apr proc mutex in my module. When I created the
mutex with APR_LOCK_DEFAULT the mutex is successfully created but I am
getting Permission Denied when I try to acquire the lock. I ran
apr_proc_mutex_defname to get the name of the default mutex type and it
is
On Wed, Aug 17, 2011 at 15:20, Jason Funk jasonlf...@gmail.com wrote:
I am trying to implement an apr proc mutex in my module. When I created the
mutex with APR_LOCK_DEFAULT the mutex is successfully created but I am
getting Permission Denied when I try to acquire the lock. I ran
Hm... interesting.
I'm creating the mutex in my post_config hook. It seems like the parent
process has to create the mutex otherwise if we want for a child a race
condition might happen
Where is the correct place to create the mutex so that it's available to all
child processes without
On 17/08/2011 09:10, Zaid Amireh wrote:
On Aug 15, 2011, at 1:45 PM, Simone Caruso wrote:
On 15/08/2011 01:44, Nick Kew wrote:
or set up something server-wide
How? there's some code that can i read?
You can use a global variable which gets set during apache's startup, you
have to
I find that if I use seteuid() to the uid of the user that my server is
running as before creating the mutex and back to root afterwards, then it
works. Is there anything wrong with this approach?
If it is a fine way of doing it, how then do I find out what user the server
is running as? I know
On 8/17/2011 1:23 PM, Jason Funk wrote:
I find that if I use seteuid() to the uid of the user that my server is
running as before creating the mutex and back to root afterwards, then it
works. Is there anything wrong with this approach?
This only works if the target path is apache-user
