No, the docs don't really clear this up.
The startup.pl stage is working, and if I look at /perl-status I see the GT and Links scripts/modules loaded into mod_perl, but those are the admin and behind-the-scenes scripts, which may be why LSQL still says it isn't running under mod_perl.
In any case, the big load-generators we need to get into mod_perl are things like search.cgi and page.cgi.
Trying to get those to work ... all the examples I see in docs assume scripts to be run under mod_perl will be put in a /perl/ directory, but obviously the location of the GT scripts is not that. The GT docs (and your examples) refer to Apache::Registry but this is replaced in mod_perl 2 by ModPerl::Registry which has some differences.
I've restarted Apache so often today I need to leave it up for a while - probably until I find someone who has this working in a similar environment.
The startup.pl stage is working, and if I look at /perl-status I see the GT and Links scripts/modules loaded into mod_perl, but those are the admin and behind-the-scenes scripts, which may be why LSQL still says it isn't running under mod_perl.
In any case, the big load-generators we need to get into mod_perl are things like search.cgi and page.cgi.
Trying to get those to work ... all the examples I see in docs assume scripts to be run under mod_perl will be put in a /perl/ directory, but obviously the location of the GT scripts is not that. The GT docs (and your examples) refer to Apache::Registry but this is replaced in mod_perl 2 by ModPerl::Registry which has some differences.
I've restarted Apache so often today I need to leave it up for a while - probably until I find someone who has this working in a similar environment.
