It occurred to me that the problem might be related to one of the
symlinks having a name, .w/, to which Apache normally wouldn't allow
access, so I tested with:

ln -s ../work w; ln -s w/mine/toys toys

but /~eddy/toys/ was also 403.  However, /~eddy/code/ has become
inaccessible too !  Yet, half an hour ago, I was able to access one of
my local URLs that does indeed go via symlinks - and it's also stopped
working now.

Something is horribly confused here ...

        Eddy.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to