Darren New wrote:
> Lan Barnes wrote:
>> If you're having reliability peoblems with Linux, speak up. Maybe someone
>> can help.
>
> Not much to say. The audio only works intermittently, and for a while it
> was just hanging about three times a week, completely locking up.
> Lately, after the latest kernel patches, it stopped doing that, so...
>
> What I'm actually fighting right now is Apache.
> I have docroot set to
> /aaa/bbb/ccc/ddd/eee/fff
> and it works fine.
>
> If I change ccc to by a symlink to a directory owned by the same user
> and all, Apache refuses to follow it. I.e., if I do
> mv /aaa/bbb/ccc /tmp/ccc
> ln -s /tmp/ccc /aaa/bbb/ccc
> Apache complains that /aaa/bbb/ccc isn't allowed to be a symlink. I have
> no idea what option to set to tell it to stop doing that.
>
Apache's default configuration refuses to follow symlinks.
Perhaps someone else will explain the rationale, but I suppose it's a
security provision. However you can override that default with a
directive for the top-level or any directory/location with an "options"
directive something like
Options FollowSymLinks
The apache documentation is quite extensive. The directives explanations
is where I find myself spending a lot of time.
In any case, it's "not fair" <tm> blaming Linux for an Apache
configuration problem ;-) In fact, I saw the same gripe in reference to
Apache in a Windows environment. (".lnk" problem).
Regards,
..jim
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
