From: Miklos S. <mi...@sz...> - 2008-04-23 05:43:42
|
> Well - i didn't work on this project recently (I focused on > KIO-GIOBridge). The code of the "streaming writes only" version based on > your patch is still here: > > http://code.google.com/p/curlftpfs/source/browse > > I don't think that optionally enabling buffered writing again would make > of sense, cause of all the problems people have had. IMHO we have to > accept that open read+write or open write+seek can not be mapped > properly to FTP. > > Probably we should just release a new version based on the code in > google svn. Good idea. Could you please do that? Oh, and here's another patch that fixes 'du' for files >= 4GB. Thanks, Miklos Index: curlftpfs-0.9.1/ftpfs-ls.c =================================================================== --- curlftpfs-0.9.1.orig/ftpfs-ls.c 2007-03-02 00:47:07.000000000 +0100 +++ curlftpfs-0.9.1/ftpfs-ls.c 2008-04-21 22:21:29.000000000 +0200 @@ -101,7 +101,7 @@ static int parse_dir_unix(const char *li if (ftpfs.blksize) { sbuf->st_blksize = ftpfs.blksize; sbuf->st_blocks = - ((size + ftpfs.blksize - 1) & ~(ftpfs.blksize - 1)) >> 9; + ((size + ftpfs.blksize - 1) & ~((unsigned long long) ftpfs.blksize - 1)) >> 9; } sprintf(date,"%s,%s,%s", year, month, day); @@ -168,7 +168,7 @@ static int parse_dir_win(const char *lin if (ftpfs.blksize) { sbuf->st_blksize = ftpfs.blksize; sbuf->st_blocks = - ((nsize + ftpfs.blksize - 1) & ~(ftpfs.blksize - 1)) >> 9; + ((nsize + ftpfs.blksize - 1) & ~((unsigned long long) ftpfs.blksize - 1)) >> 9; } } |