This is what I've found:
Using
completely breaks browsing FTP in FileZilla. All directories are seen as regular files and are not accessible in FileZilla. Though no issues in FAR for example.
ProFTPd failed to restart properly on my new CentOS 6 box, so the fact the symlinks were working fine, I guess, was caused that the old version of ProFTPd was not killed and was still running. After forced restart symlinks are no more accessible in FileZilla.
With ProFTPD 1.3.4b symlinks are not shown in FAR, EditPlus (the list might include some other FTP clients), if a reference to a directory or file begins with dot-and-slash, e.g.:
if to change to
then the symlink can be seen in FAR, EditPlus (the list might include some other FTP clients). But it still makes no difference for Filezilla.
So I'd agree this is a ProFTPD/Filezilla problem.
Using
Code:
FactsAdvertise off
ProFTPd failed to restart properly on my new CentOS 6 box, so the fact the symlinks were working fine, I guess, was caused that the old version of ProFTPd was not killed and was still running. After forced restart symlinks are no more accessible in FileZilla.
With ProFTPD 1.3.4b symlinks are not shown in FAR, EditPlus (the list might include some other FTP clients), if a reference to a directory or file begins with dot-and-slash, e.g.:
Code:
public_html -> ./domains/domain.com/public_html
if to change to
Code:
public_html -> domains/domain.com/public_html
then the symlink can be seen in FAR, EditPlus (the list might include some other FTP clients). But it still makes no difference for Filezilla.
So I'd agree this is a ProFTPD/Filezilla problem.