l.d.m: Good catch and something that should work. I believe the problem is in ioFTPD's internal resolving algorithm. During the resolving of the VFS path to the Real path it finds the existing directory of the same name (since windows is itself case insensitive) and it doesn't notice or care that the cases differ.
I'm not sure if I'll change the rename command to use the same case as the input string by fudging the Real path returned by the resolver, or if I'll change the resolver itself to preserve the case of the input string. Either will work, though I'm not sure what happens with mountpoints...
I'll add it to the list next update. For a very short term solution either modifying the file directly in the filesystem if your the admin, use a very simple script to do the rename yourself, or rename "test" to "testa" to "TEST" which should work provided there aren't any active transfers below the path which might lock the directory tree from being renamed.
|