similar to: rsync: mkstemp failed: No such file or directory (2)

I've released rsync 2.6.5pre1. This release is mainly a bug-fix release for some problems in the 2.6.4 release, but it also has a few minor enhancements. To see all the changes since 2.6.4, go here: http://rsync.samba.org/ftp/rsync/preview/rsync-2.6.5pre1-NEWS You can grab the tar file and its signature from here: http://rsync.samba.org/ftp/rsync/preview/rsync-2.6.5pre1.tar.gz

I've released rsync 2.6.5pre1. This release is mainly a bug-fix release for some problems in the 2.6.4 release, but it also has a few minor enhancements. To see all the changes since 2.6.4, go here: http://rsync.samba.org/ftp/rsync/preview/rsync-2.6.5pre1-NEWS You can grab the tar file and its signature from here: http://rsync.samba.org/ftp/rsync/preview/rsync-2.6.5pre1.tar.gz

Pardon me if this is already known -- Theo, at least, had never heard of a Unix doing this. mkstemp() under Linux claims to conform to BSD4.3, but BSDs (FreeBSD and OpenBSD, at least) seem to have a slightly different behavior. Under Linux, new files are created with mode 0666, while under BSDs new files are created with mode 0600. A user need only set his umask to 0 and he will be able to

http://bugzilla.mindrot.org/show_bug.cgi?id=508 Summary: Krb4/AFS token passing doesn't work because of mkstemp Product: Portable OpenSSH Version: -current Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org

https://bugzilla.samba.org/show_bug.cgi?id=1605 Summary: Copy from NTFS to VFAT produces mkstemp and stat errors Product: rsync Version: 2.6.2 Platform: x86 OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

https://bugzilla.samba.org/show_bug.cgi?id=2790 Summary: mkstemp fails for paths which include extended (8-bit) characters Product: rsync Version: 2.6.5 Platform: All OS/Version: Mac OS X Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org

Hello all I have two Linux boxes. The first one is samba servers for the Windows clients. The second one is backup storage. So every few hours rsnc synchronises the data directories on the second machine. They are Suse Linux 9 Linux max 2.6.11.4-21.7-smp #1 SMP Thu Jun 2 14:23:14 UTC 2005 i686 i686 i386 GNU/Linux rsync version 2.6.3 protocol version 28 From time to time I get errors reported,

Hi, --- + rsync -av --timeout 120 /home/20070129_1012/status.csv --port 5873 fileserver::test/20070129_1012/status.csv building file list ... done status.csv rsync: mkstemp "/20070129_1012/.status.csv.IWS933" (in test) failed: No such file or directory (2) sent 347 bytes received 38 bytes 770.00 bytes/sec total size is 228 speedup is 0.59 rsync error: some files could not be

http://bugzilla.mindrot.org/show_bug.cgi?id=44 ------- Additional Comments From jan.iven at cern.ch 2002-07-05 01:11 ------- Update: I have reported this to the glibc people, who say that they will not modify their mkstemp(). (http://bugs.gnu.org/cgi-bin/gnatsweb.pl?debug=&database=default&cmd=view+audit-trail&cmd=view&pr=3573) Attached is a patch to configure{ac,in} to

https://bugzilla.samba.org/show_bug.cgi?id=11978 Bug ID: 11978 Summary: mkstemp failed: File name too long (36) when filename is under the limit Product: rsync Version: 3.1.1 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core

The setup... Transport is via SSH. BoxA : Ubuntu 8.10 BoxB : Mac OS X 10.4.11 If I use rsync v2 to transfer data from BoxA to BoxB everything works fine. However, if I use rsync v3 to transfer the data, the following error is reported : rsync: mkstemp "/path/to/somefile/file.pm.JKQczN" failed: No such file or directory (2) If at all possible,

Hello, The remote rsync process will call the mkstemp library call whenever it's updating (or uploading, I'm not sure) a new file. The mkstemp call uses a pathname that does not place the temporary file in the same directory as the updated file. In my case the permissions for these directories are different, and I get a "Permission denied" error message. Here is my Rsync

We are using rsync to push DNS records from one machine (running rsync 2.5.6 as a client process on Debian woody) to a collocation server ( running rsync 2.5.6 as a daemon on RedHat 7.3). To test this process we are using a script that pushes one file from the Debian box to the collocation server. It appears that a file transfers, but upon checking there is no file transfer and an error in the

Hi, I am a new user and tried at least some of the recommended ways to find an answer to my question (search the net, ask IT professionals). But when everything fails nothing beats newsgroups... Here is my problem. I compiled rsync 2.6.2 on a Tru64 v5.1b system. I am trying to use rsync to backup data to a NFS mounted disk outside our immediate local network. Needless to say that rsync works

We are trying to enable large file support for everything built for ARM on ChromeOS and openssh uses mkstemp which has a 64-bit version for compatibility with open64. When looking into enabling the large file support flags, I noticed: `void start_progress_meter(const char *, off_t, off_t *);` in progressmeter.h which would have different ABIs with and without large file support. You all

On Wed, 22 Mar 2023, Allen Webb wrote: > We are trying to enable large file support for everything built for > ARM on ChromeOS and openssh uses mkstemp which has a 64-bit version > for compatibility with open64. When looking into enabling the large > file support flags, I noticed: > > `void start_progress_meter(const char *, off_t, off_t *);` > > in progressmeter.h

Hello, Please let me know if this is a bug or a feature. I used to be able to do the following with 2.5.5. On a remote host I have /mytree and I mirrored at my local host as a regular user doing rsync -avz --delete kent@host:/mytree /. with 2.5.6 I get mkstemp .file.aFhK3N failed: Permission denied probably because rsync2.5.6 is attempting to create a temporary file on the root directory,

http://bugzilla.mindrot.org/show_bug.cgi?id=44 ------- Additional Comments From djm at mindrot.org 2002-05-13 15:39 ------- Have you filed a bug in the glibc bug tracking system? BTW, how did you compile with krb4 on Redhat 7.2 without running over libdes conflicts? ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=44 djm at mindrot.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From djm at mindrot.org 2003-01-07 15:18

http://bugzilla.mindrot.org/show_bug.cgi?id=44 djm at mindrot.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ksulliva at psc.edu ------- Additional Comments From djm at mindrot.org 2003-03-13 09:43 ------- *** Bug 508 has been marked as a