similar to: mkstemp fails but data still transferred

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,

Hi all, I think I just found a small bug in rsync... It has costed me about half an hour searching for a problem which actually didn't exist! If you use rsync like this: > rsync --password-file=/tmp/non-existing-file /tmp/somefile foo@bar::tmp/ Rsync will ask for the password since the supplied file doesn't exist: > rsync: could not open password file

Hi guys, samba client version 3.0.5, server version 3.0.5, kernel 2.4.26. Relevant configs on server: unix extensions = Yes wide links = Yes follow symlinks = Yes On client computer with home user mounted via smbfs I'm trying this: D102-054 [/lp/home/dito/tmp] > cd /tmp D102-054 [/tmp] > mkdir dest_dir D102-054 [/tmp] > cd - D102-054 [/lp/home/dito/tmp] > ln -s /tmp/dest_dir

https://bugzilla.samba.org/show_bug.cgi?id=8130 Summary: ACL and link-dest do not work together Product: rsync Version: 3.0.8 Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: az9901 at gmail.com

?s 23:06 de 25/07/2023, Bob Green escreveu: > Hello, > > I am seeking advice as to how I can download the 833 files from this > site:"http://home.brisnet.org.au/~bgreen/Data/" > > I want to be able to download them to perform a textual analysis. > > If the 833 files, which are in a Directory with two subfolders were on > my computer I could read them

https://bugzilla.samba.org/show_bug.cgi?id=5802 Summary: misleading error message in atomic rsync Product: rsync Version: 3.1.0 Platform: All OS/Version: Linux Status: NEW Severity: trivial Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: normalperson@yhbt.net

I realize batch mode is still experimental, but I was hoping there might be a workaround for a problem I am getting. I have been trying to run some tests and I get the below error when I use the --read-batch option to. I can successfully create an initial set of batch files, then a second set based upon a few modified test files from the first batch. When I first run the --read-batch option

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 ------- 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

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=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

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

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

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

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