Oh great mod_perl sages...I beseech thee on bended knee ( with eyes
averted) :>)
I'd like to preface this by saying that I _hate_ to ask lists for help, so
do all I can to research the problem on my own... but I'm not sure I'm even
looking in the right place. I've read the mod_perl guide (have it printed
and in a binder, in fact). Any assistance (including pointing me in the
right direction) would be greatly appreciated.
I'm running Apache 1.3.9/mod_perl1.21 on a Mac Workgroup Server, LinuxPPC
(1999). I have a group calendar script (FrameCal,
http://www.blue-gecko.com/framecal ) that is giving me problems.
Actually, I have one calendar working perfectly with no problems. You are
supposed to be able to create additional calendars that use the same
script. Each calendar has it's own separate folder (with it's own separate
characteristics set in a .conf file). You pass the calendar information
when you call the script. ( action
="URLtoScript/framecal.pl?calendar=whichCalendar".
The problem is that the 2nd calendar has it's own set of authorized users ,
and event catagories. It will work fine for a while when I restart Apache,
but before long it will not let it's users log in. Checking out the drop
down menu it becomes apparent that you are looking at the catagories for
THE OTHER calendar. Restarting the server fixes the problem again for a
while.
I thought that setting up entirely different framecal scripts in entirely
different folders for the two calendars would solve the problem. So, the
script that works is in
/cgi-bin/calendar/admissions/framecal.pl
and the script that doesn't work is in
/cgi-bin/newscalendar/news/framecal.pl
but the information from the one calendar is still being confused by the
server with the other (though apparently not vice-versa).
I believe that I have both locations set up with the exact same
permissions/access restrictions, but I suspect that I am missing something
that involves the mod_perl aspects of the apache httpd.conf.
Is there something that I can learn from calling myserver.edu/status or
/perl-status? (It looks like I need to recompile with Devel::Sydump to get
much info from perl-status... if I knew what to do with it.)
Maybe more info than you need to know, but... here is the list of Apache
compiled-in modules...
http_core.c
mod_env.c
mod_log_config.c
mod_mime.c
mod_negotiation.c
mod_status.c
mod_include.c
mod_autoindex.c
mod_dir.c
mod_cgi.c
mod_asis.c
mod_imap.c
mod_actions.c
mod_userdir.c
mod_alias.c
mod_access.c
mod_auth.c
mod_setenvif.c
mod_perl.c
Thanks for any ideas you might have to share.
Darren Addy
University of Nebraska at Kearney
