The problem was fairly hidden.
It turns out that one of the directories in the PATH of the symbolic
link did not have the search bits enabled (permissions). Once that was
adjusted, it worked fine.
This turns out to be a problem with Apache-2, since it should report a
better (unambiguous) error - there is a bug report filed about it.
Thanks.
Julien Gabel wrote:
Using FreeBSD_6.0_Beta4 (applies to Beta2, also).
Not related to FreeBSD versions, i think.
I'm trying to track down a problem I've been having with apache-2.0.54
not following symbolic links.
It's basically come down to my being able to follow the link if it's in
the same directory structure (ie: .. or /path/to/..), but fails if the
symbolic link is located elsewhere (ie: /usr/local/path/directory) or on
another disk.
It is the `normal' behaviour for Apache, AFAIK.
I wonder if there's a sysctl or other system variable that handles the
behavior of or access to symbolic links in this fashion that I may have
missed. Seemed like a reasonable conclusion after these tests have
been failing, though it could be something else, too.
Don't know if it is possible (and advisable) to succeed in following an
external link this way. More help/answers may be obtain from the Apache
people, since it seems more an httpd configuration trick, than a FreeBSD
one.
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
