I did not know that I need to have my list in shared memory (I assume that's what you're referring to as shm in your response). This is the type of thing that I wanted to know in my question. Is there a way to add my linked list into shared memory? I will search for this on the web, but a quick heads-up on how to do this would be much appreciated. Also, what is modules@ ? Respectfully, Pranesh -----Original Message----- From: Tom Evans [mailto:tevans.uk@xxxxxxxxxxxxxx] Sent: Wednesday, November 16, 2011 7:26 AM To: users@xxxxxxxxxxxxxxxx Subject: Re: Apache 2.2.3 Session tracking On Tue, Nov 15, 2011 at 8:40 PM, Pranesh Vadhirajan <vadhirajan@xxxxxxxxxxxxxx> wrote: > Should something be modified in Apache modules when maintaining persistent > memory? I am having a problem with a linked list implementation that I > wrote which I am linking with my apache module to maintain a list of > sessions so that I can track web sessions connecting to our web site at > work. I have no trouble when using this linked list implementation outside > of Apache ( I have a simple test file written in C that simulates sessions > and I do not have any problems when running the test), however when I test > my module in apache on “real” data, I notice that my linked list is seen as > null in situations when it should not be so. I can attach relevant parts of > my code if needed, but I would like to know if there are any known steps > that need to be taken for apache to properly maintain thread safety. I am > using semaphores to protect the integrity of my linked lists across threads > defined in the semaphore.h header file. > > > > Respectfully, > > Pranesh How are you sharing your list between children? Is your linked list in shm? This might be better directed at modules@ Cheers Tom --------------------------------------------------------------------- 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
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
|