Compiled Slash with SLASH_PREFIX=/home/slash and
installed into /home/slash. (Yes, I realize that's not
recommended, but installing into /usr/local/slash
doesn't fit in well with the FreeBSD directory
structure.) All of the http config files and all of
the vars in the database point to /usr/home/slash.
It's probably important to point out that in
FreeBSD, /home is a symlink to /usr/home.
The problem arises if users are actually paying
attention to their httpd configs and change them to
point to the actual install directory (/home/slash).
Apache will restart just fine and the slash site will
come up, but any of the http://example.com/my/ links
will be broken due to ExecCGI not being set
for /usr/home/slash. Obviously this becomes difficult
to debug without knowing to look in the vars db for
the settings.
Also, the logs setting in the site config file are not
absolute (they point to log/sitename.log) and since
FreeBSD does not have a /usr/local/logs/ directory,
Apache errors out on restart. It would seem to make
more sense to point these entries to
$SLASH_PREFIX/site/$SITENAME/logs.
Log in to post a comment.
