vsftp: 550 failed to change directory on symlinks
I use anonymous ftp to distribute installation files for a software program. The pub directory tree is set up by software version number, with a "current" folder containing symbolic links to files in other directories named for specific versions. Thus, the contents of "current" contain the most recent files (links) regardless of what version the actual files came from. When I release new files, I just symlink to the updated files. This worked great on my old server using ProFTP. Using vsFTP now, whenever I try to follow a link I get an error: vsftp 550 failed to change directory The links are linked to valid paths. In visual ftp clients, the links appear with folder icons. What's up here? Rob ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
On Tuesday 26 July 2005 02:25 pm, bronto@csd-bes.net wrote:
I use anonymous ftp to distribute installation files for a software program. The pub directory tree is set up by software version number, with a "current" folder containing symbolic links to files in other directories named for specific versions. Thus, the contents of "current" contain the most recent files (links) regardless of what version the actual files came from. When I release new files, I just symlink to the updated files.
This worked great on my old server using ProFTP. Using vsFTP now, whenever I try to follow a link I get an error:
vsftp 550 failed to change directory
The links are linked to valid paths. In visual ftp clients, the links appear with folder icons.
What's up here?
vsftp disallows following symlinks by default. See the docs on how to change that. -- _____________________________________ John Andersen
Quoting John Andersen <jsa@pen.homeip.net>:
On Tuesday 26 July 2005 02:25 pm, bronto@csd-bes.net wrote:
I use anonymous ftp to distribute installation files for a software program. The pub directory tree is set up by software version number, with a "current" folder containing symbolic links to files in other directories named for specific versions. Thus, the contents of "current" contain the most recent files (links) regardless of what version the actual files came from. When I release new files, I just symlink to the updated files.
This worked great on my old server using ProFTP. Using vsFTP now, whenever I try to follow a link I get an error:
vsftp 550 failed to change directory
The links are linked to valid paths. In visual ftp clients, the links appear with folder icons.
What's up here?
vsftp disallows following symlinks by default. See the docs on how to change that.
-- _____________________________________ John Andersen
Are you referring to the note that says that symlinks aren't followed when chroot_local_user=YES? I saw that prior to posting here, but it didn't make sense to me that this was the issue since this is an anonymous ftp issue, and "anon" isn't a local user. In any case, at your suggestion I disabled it but the symlinks still don't work. That's the only mention I see of symlinks in the docs. Rob ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
participants (2)
-
bronto@csd-bes.net
-
John Andersen