---The news so far for benefit of the mailing list--- I have a fairly plain vanilla install of the Secure Web Server on top of RH 5.1 all running on a 100MHz Pentium. Apache-ssl works fine, so far as I''ve seen so far, with the exception of mod_perl. All my scripts, either in a "perl directory" using the sample configuration shipped with apache-ssl or *.pl files controlled with a <Files *.pl> directive, are served by apache-ssl as text/plain listings of the source code. No error messages in the logs. Unfortunately, I did some upgrades and additions using the CPAN module *before* I tested Apache::Registry, so I can''t swear that it doesn''t work out of the box. ---And now for the current news for the trouble ticket and others--- Just in case some of the upgrades/installs of perl modules I did broke things, I did a rpm -e --nodeps perl, deleted the remaining contents of /usr/lib/perl, and did a rpm -e mod_perl. I then used rpm to reinstall perl-5.004-6.i386.rpm for RH 5.1 and mod_perl-1.08-1glibc.i386. As expected, trying to start apache_ssl before I''d restored mod_perl resulted in rude error messages about the mod_perl configuration statements and even after I restored mod_perl, I got error messages about Apache::ePerl being missing (given that I''d blown away everything in /usr/lib/perl). After I commented out all references to Apache::ePerl (but left all the Apache::Registry stuff in) the server started up fine. This indicates to me that the server is finding the mod_perl files and that at a certain level things are working. However, as before, perl files are simply served as text/plain listings of the source code. No error messages in logs. No hint (unless I''m being real dense here) of what''s going wrong. Any ideas? --Jon Radel jon@radel.com