Hello,
I have got a funny situation with my ftp server, I am not yet sure if this is a client side issue or an actual application fault.
when a client logs into his FTP account , normally one would expect a symlink to public_html -> ./domains/example.com/public_html
the symbolic link works fine if i try to access it via ftp from command line, but while trying to access it using FlashFXP ( both ver 3 and 4 ) , and filezilla - the Link is displayed as a regular file, and is not followed.
as this is not an issue for me as an admin who uses the command line, the issue currently affects all windows clients ( hosting clients ) , which try to use symlinks on this server.
I have tried to update proftpd to the latest version today ( ~]# proftpd -v
ProFTPD Version 1.3.4a) , this did not resolve the client side issue.
Quite oddly, on another server of mine which runs ProFTPD 1.3.3c, there is no issue for the windows clients to follow symlinks.
searching the forums lead to this:
http://www.directadmin.com/forum/showthread.php?t=40404&highlight=symlink
which lead to this:
http://www.proftpd.org/docs/howto/Chroot.html
Basically , they explain that a symlink within a chrooted directory must be in a path relative to the chrooted directory.
so make sure NOT to:
ln -s public_html /home/example/domains/example.com/public_html
and YES to:
cd /home/example/
ln -s public_html ./domains/example.com/public_html
I have done that, but still no luck with the client, it sees the symlink not as a "directory" which i can click , but as a regular file(as everything is) which windows cannot understand what to do with.
to better explain what we see as a client , view attached png:

Any advice is more then welcome.
I have got a funny situation with my ftp server, I am not yet sure if this is a client side issue or an actual application fault.
when a client logs into his FTP account , normally one would expect a symlink to public_html -> ./domains/example.com/public_html
the symbolic link works fine if i try to access it via ftp from command line, but while trying to access it using FlashFXP ( both ver 3 and 4 ) , and filezilla - the Link is displayed as a regular file, and is not followed.
as this is not an issue for me as an admin who uses the command line, the issue currently affects all windows clients ( hosting clients ) , which try to use symlinks on this server.
I have tried to update proftpd to the latest version today ( ~]# proftpd -v
ProFTPD Version 1.3.4a) , this did not resolve the client side issue.
Quite oddly, on another server of mine which runs ProFTPD 1.3.3c, there is no issue for the windows clients to follow symlinks.
searching the forums lead to this:
http://www.directadmin.com/forum/showthread.php?t=40404&highlight=symlink
which lead to this:
http://www.proftpd.org/docs/howto/Chroot.html
Basically , they explain that a symlink within a chrooted directory must be in a path relative to the chrooted directory.
so make sure NOT to:
ln -s public_html /home/example/domains/example.com/public_html
and YES to:
cd /home/example/
ln -s public_html ./domains/example.com/public_html
I have done that, but still no luck with the client, it sees the symlink not as a "directory" which i can click , but as a regular file(as everything is) which windows cannot understand what to do with.
to better explain what we see as a client , view attached png:

Any advice is more then welcome.