rsync: mkstemp "/20070129_1012/.status.csv.IWS933" (in test)
failed: No such file or directory (2)
shaibn at gmail.com
Fri Feb 2 05:58:56 GMT 2007
Thanks for the info.
The new Debian Sarge server I built is using 2.6.9 version of rsync which
before, was not that new. It used to work fine (as far as I can tell you)
that sending a single file, would also create the directory if it did not
exist. Am I wrong to say this? Ever since the new server came up, rsync
failed when I sent this file first before the directory was there.
I don't want to send the entire directory, since it contains many other
files that don't interest me and whice would slow down my cycles.
On 2/1/07, Matt McCutchen <hashproduct+rsync at gmail.com> wrote:
> On 1/29/07, Shai <shaibn at gmail.com> wrote:
> > + rsync -av --timeout 120 /home/20070129_1012/status.csv --port 5873
> > fileserver::test/20070129_1012/status.csv
> > rsync: mkstemp "/20070129_1012/.status.csv.IWS933" (in
> > test) failed: No such file or directory (2)
> Since you want the file to have the same name "status.csv" on the
> destination as on the source, you can omit that name from the
> destination path: "fileserver::test/20070129_1012/". This will have
> the same effect except that rsync will create the directory
> "20070129_1012" if it doesn't exist before trying to receive a file
> into it.
> Note to people who might encounter this message in the archives: since
> rsync 2.6.7, when the receiver is receiving a single file that is not
> a directory, it tries to change into the containing directory first.
> Thus, people who try the original command with rsync 2.6.7 or newer
> should see a "push_dir" error instead of a "mkstemp" error.
-------------- next part --------------
HTML attachment scrubbed and removed
More information about the rsync