similar to: [Bug 2790] New: mkstemp fails for paths which include extended (8-bit) characters

https://bugzilla.samba.org/show_bug.cgi?id=2790 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|major |enhancement Status|NEW |ASSIGNED Summary|mkstemp fails for paths |Add support for

hello, I'm trying to use a remote SMB/CIFS share to backup a local directory tree. I use rsync "version 3.0.4 protocol version 30" and mount.cifs "1.10" with a kernel 2.6.18. The directory I'm trying to backup is quite big and has a lot of files inside. [root@linux dir]# du -hs . 50G . [root@linux dir]# find . -type f | wc -l 41929 I get the following error when

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

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,

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:

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

This uses time, ASLR and pid for randomisation. (Closes: #516774) Signed-off-by: Thorsten Glaser <tg at mirbsd.org> --- usr/include/stdlib.h | 2 + usr/klibc/Kbuild | 2 +- usr/klibc/mkstemp.c | 93 ++++++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 96 insertions(+), 1 deletions(-) create mode 100644 usr/klibc/mkstemp.c diff --git a/usr/include/stdlib.h

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

I'm not really what you would call a linux newbie, but I managed to run into a problem with rsync that has me stumped. I want to conduct un-attended backups of various files and directories over about 3000 miles of Internet, so I chose sshd and rsync for the job. I wrote a pair of scripts to do the job, the first to run incremental tars on the localhost, the second to run the rsync client.

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

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=5472 Summary: FreeBSD 3.0.3pre2 'make check' failures Product: rsync Version: 3.0.3 Platform: Other OS/Version: FreeBSD Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

https://bugzilla.samba.org/show_bug.cgi?id=5473 Summary: OS-X Leopard Rsync 3.0.3pre2 make check failures Product: rsync Version: 3.0.3 Platform: Other OS/Version: SunOS Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

https://bugzilla.samba.org/show_bug.cgi?id=5470 Summary: Make check failures on Solaris 10 with rsync 3.0.3pre2 Product: rsync Version: 3.0.3 Platform: Other OS/Version: SunOS Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

https://bugzilla.samba.org/show_bug.cgi?id=5297 Summary: merge test fails Product: rsync Version: 3.0.0 Platform: Other OS/Version: SunOS Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: bfriesen@simple.dallas.tx.us QAContact:

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

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,

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

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