in reply to Checklist for installing mod_perl

At risk of stating the obvious, and without studying every line of your log, it seems your next step is to give the server some content to serve, preferably some of it generated via mod_perl. Anyone who can get thru this far presumably knows that's next.

So please say what you want. If it's just congratulations, then congratulations!

cmac

Replies are listed 'Best First'.
Re^2: Checklist for installing mod_perl
by wfsp (Abbot) on Apr 06, 2010 at 10:41 UTC
    Thanks for your comments.

    ...give the server some content to serve...
    Agreed. I'm planning a further post on that. While not perl it may be worth first discussing where to put the content/scripts etc.

    For instance, the default DocumentRoot I have is currently /opt/httpd/htdocs. I think I would prefer it out from under the feet of Apache under either the user or perhaps, looking ahead to more than one user updating the website, under /var/www/mydomain/perl and /var/www/mydomain/docroot.

    Also not perl, how to handle particular directories that the Apache user could write to, for example a file upload directory under DocumentRoot and a directory that perl could write to e.g. sessions/logs. Perhaps consider setting up users and groups to help with the job.

    And after sorting that out, some perl scripts. :-)

    All that may have been a distraction so I decided not to cover it this time.