View Single Post
Old 06-24-2010, 03:54 AM  
exjoe
Junior Member
 
Join Date: Nov 2009
Posts: 3
Default

Timestamps: I see, but the quirk here seems to be that there are two spaces between the Day and Year for the old items. I'm fairly certain this isn't an error in the client, but I'll see if I can generate some test cases and find out.

STAT -alT does produce the output the client expects, without the double-space before the year:
Code:
4:50:07 AM > stat -alT
4:50:08 AM 212-Status of .:
4:50:08 AM drwxr-xr-x   2 ioFTPD       ioftpd                0 Jun 23 02:24:15 2010 .
4:50:08 AM drwxr-xr-x  26 ioFTPD       ioftpd       14357552240 Jun 24 05:36:46 2010 Dir2
4:50:08 AM drwxr-xr-x  51 ioFTPD       ioftpd       10748424602 May 16 05:57:43 2010 Dir6
4:50:08 AM drwxr-xr-x  37 ioFTPD       ioftpd       7482858336 Jun 10 04:47:25 2010 Dir3
4:50:08 AM drwxr-xr-x 102 ioFTPD       ioftpd        386708274 Mar 01 06:20:32 2009 Dir5
4:50:08 AM 212 End of Status
Mountpoints: Nothing regarding VFS warnings, and I am indeed running this as a regular process. Dir1 and Dir2 are both user directories under the user running ioFTPD (User1), and Dir6 and Dir7 are both for the same user (User2) (the two users are from different OS environments).

All of these directories are simple, nothing is being accessed over the network, and as far as I know there aren't any junctions or anything out of the ordinary.

All users have read and execute access, and all administrators have full control over all 7 directories. I've tried running ioFTPD with administrative rights, and this doesn't solve the problem either.
exjoe is offline   Reply With Quote