Originally Posted by digitalnerds
I wasnt clear enough. You may add a new directive for /home/cricket/cricket it doesnt matter. Your /var/www/html will not be able to follow links outside /var/www/html. In your case apache will refuse to follow symlinks inside /var/www/html that leads to /home/cricket/cricket. I repeat myself "if your symlink target dir is outside the directory for which you enabled FollowSymLinks your apache will not be able to follow the symlink." So you do not need to add:
Options FollowsymLinks ExecCGI
because the most you will is to specify that all symlinks inside /home/cricket/cricket are to be followed within the boundaries of the PATH apache uses to access those files.
I don't know if you are running the 2.6 kernel with SELinux enabled, but here is something else to consider:
Don't forget to also check SELinux permissions on the directory with
ls -Z /home/cricket/cricket
You may have to run
chcon -R --reference /var/www/html /home/cricket/cricket
to allow the web server to read the files.