On 05/20/10 12:12, Perrin Harkins wrote:
On Thu, May 20, 2010 at 11:12 AM, Chris Bennett
wrote:
Well I'm pretty clueless. It works fine on nearly identical desktop at home.
Won't work on server.
That means the problem is either different versions on the one that
doesn't work or a configurati
On Thu, May 20, 2010 at 11:12 AM, Chris Bennett
wrote:
> Well I'm pretty clueless. It works fine on nearly identical desktop at home.
> Won't work on server.
That means the problem is either different versions on the one that
doesn't work or a configuration mistake (more likely). My advice is
to
On Thu, May 20, 2010 at 11:17 AM, Some Guy wrote:
> If the MPM is threaded, a rwlock is used where the cleanup obtains the
> writelock and request handlers are obtaining a read lock.
You don't need to do this. Variables are not shared between perl
threads unless you make them shared. If you avo
I tried the cleanup handler solution, and threw a sleep in there for ha
has. Basically I do the following in my handler:
Register a cleanup on the request's pool
Check if I need to do something to the user agent if it is found in an array
that is backed by a data file
If it's not in the array, de
Well I'm pretty clueless. It works fine on nearly identical desktop at home.
Won't work on server.
I don't know what else I can try.
I have tried using Location instead of Directory.
Changed module names.
Fiddled with startup.pl
Still always get uri as /perl/login.pl and creds as uninitialized.
This module is meant for other parties to use, so I can't define what MPM
they use. I would like it to work in either case. I don't mind throwing in
locking logic based on the results of querying whether the MPM is threaded
or not - I just want to better understand that scenario and how it applie
On 05/20/2010 08:54 AM, Some Guy wrote:
The cleanup handler is a brilliant idea. That removes the need for a
polling thread. If I attach the cleanup to the request's pool and run
in a threaded MPM, this led to contention for the globals that I'm
updating in C. Is this the case with PerlModules
The cleanup handler is a brilliant idea. That removes the need for a
polling thread. If I attach the cleanup to the request's pool and run in a
threaded MPM, this led to contention for the globals that I'm updating in
C. Is this the case with PerlModules, or can I get away without locking
them?
On Wed, May 19, 2010 at 6:36 PM, David wrote:
> If I haven't sent this to the correct place please inform me.
>
> I've look through the assorted documentation, both mod_perl and Apache, and
> haven't found a solution to my situation. I've also given the internet a try
> with no luck. I admit I'm n
