Hi, I have to sync two directories and one is an ftp mount. I had to set a different tmp dir as tmp files are not allowed in ftp mounts so I see no point in copying things to a temp dir if they won't be used for the transfer. Is there any way to eliminate the use of a tmp dir? If not, could it be a feature request? Regards,
On 28.01.2014 08:35, Juan Pablo Lorier wrote:> Hi, > > I have to sync two directories and one is an ftp mount. I had to set a > different tmp dir as tmp files are not allowed in ftp mounts so I see no > point in copying things to a temp dir if they won't be used for the > transfer. > Is there any way to eliminate the use of a tmp dir? If not, could it be > a feature request?rsync doesn't use a tmp-directory by default. The default is to make it a "."-file with an additions random extension to the filename. So in your case there should be a commandline (rsync.conf?) option set that does that (If i read the man-page correctly, it's -T/--temp-dir). Just remove it and rsync falls back to default behaviour. If you don't want tmp-files at all, with "--inplace" you instruct rsync to change files "inplace", but you should read the man-page for the gotchas. -- Matthias
On 28.01.2014 08:35, Juan Pablo Lorier wrote:> Hi, > > I have to sync two directories and one is an ftp mount. I had to set a > different tmp dir as tmp files are not allowed in ftp mounts so I see no > point in copying things to a temp dir if they won't be used for the > transfer.What do you mean by ftp mount? fuse? Is that on Linux or something else? If you DON'T sync to a regular filesystem, there are (or can be) limitations on what kind of basic operations are allowed on a file. So follows the second questions: Can rsync cope with the limitations. Which would explain the I/O-error in the other mail, rsync --inplace does something that isn't allowed/supported. But IFF it isn't a regular filesystem you are syncing to, the value of using rsync for the job is largely reduced. Rsync's strength for remoted transfers is "delta transfer" which can't be used in such a setup. In that setup rsync is reduced to a glorified "cp" (ignoring the capability to delete files). You could just use cp directly. And with "-u" you also have the basic capability to not copy files that didn't change in between runs. (Maybe with an added "-a", or at least "--preserve=timestamps") -- Matthias