similar to: [patch] rsync large file support on AIX and HPUX

https://bugzilla.samba.org/show_bug.cgi?id=5027 Summary: Perms in do_mkstemp are not always valid Product: rsync Version: 2.6.9 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: cmadams@hiwaay.net

Why is do_mkstemp fchmod-ing the temporary file? I was not able to figure this out from the CVS logs or my searches in the mail archives. Currently, do_mkstemp does this (*): mkstemp temporary file (which leaves it with 0600) fchmod temporary file (final perm & 0700) And then later it gets renamed to the final name and permissions set to what they are supposed to be. (*)

I have discovered that rsync 2.5.6 uses the mkstemp() routine wich do not have a 64bits version into the AIX libc. A very simple workaround to the big files writing rsync pb. is to not use this routine that create files w/ mkstemp() by modifying the "syscall.c" source file at line 154 as following : #if defined(HAVE_SECURE_MKSTEMP) && defined(HAVE_FCHMOD) become #if

Hi, on AIX, mkstemp doesn't open a file with the O_LARGEFILE option, so you can't transfer files > 2GB to an AIX machine. Here is a fix: diff -c -r rsync-2.5.6.orig/syscall.c rsync-2.5.6/syscall.c *** rsync-2.5.6.orig/syscall.c Sun Jan 26 21:09:02 2003 --- rsync-2.5.6/syscall.c Wed May 14 13:55:15 2003 *************** *** 151,157 **** if (dry_run) return -1; if

Thanks. I am still not sure whether option "with-acl-support" has been compiled in the smbd. The following is the output: Build environment: Built by: root@hxwu-dt-tt Built on: Tue Dec 23 15:00:40 CST 2003 Built using: gcc Build host: SunOS hxwu-dt-tt 5.9 Generic_112233-08 sun4u sparc SUNW,Sun-Blade-100 SRCDIR: /space/hxwu/swinstall/samba-3.0.1/source

Has anyone successfully gotten the VFS modules to work under AIX 5.3 and Samba 3.0.x ? I have no problem compiling Samba 3.0.x and having it working; but when I set up a VFS module the following occurs: 1. In the log file I see: [2005/11/09 15:45:02, 0] lib/fault.c:fault_report(36) =============================================================== [2005/11/09 15:45:02, 0]

I'm curious to know where the tdbsam password database file is kept on my Fedora 7 system. Using the unmodified smb.conf file that shipped with Fedora 7, I've enabled users using smbpasswd, and successfully accessed shares. I just can't figure out where the password database is located: [root@box ~]# service smb start [root@box ~]# setsebool samba_enable_home_dirs on [root@box ~]#

Hello, I'm trying to set up samba using ADS for authentication. I can successfully join the samba machine to the domain. Windows hosts can "see" the samba machine. After successfully joining, doing: # wbinfo -u shows me ADS-defined users. Same goes for groups. However, when I try and assign one of those users ownership of a file, I get: # chown user1 /tmp/test chown: test1:

So I am compling the newest release of samba 3.0.14a on Solaris 2.8. I can get it to compile but I don't get all the built in modules that I should and smbd when fired up bombs out with something like, ------- derek@supernova:/opt/UMsmb/sbin# ./smbd -c /etc/samba/smb.conf -i smbd version 3.0.14a started. Copyright Andrew Tridgell and the Samba Team 1992-2004 No builtin nor plugin backend for

I've got some problems with file access control on a linux-server with samba 3.0.14a compiled from a src-rpm. This is the method I've been using for the past 5-6 releases. It's a redhat 8.0 machine and the kernel version is 2.4.30. The problems seem to have appeared since upgrading from 3.0.13. Symptom 1: When using force group on a share, users from the two groups edb and

Sftp fails to correctly preserve permissions when fetching a file. It adds write permission for the owner (presumably so it can write the file). Sftp also fails to preserve the uid/gid. Added code so that if is running as root, uid and gid are preserved. patch is based on Openssh 3.4p1. *** sftp-client.c@@\main\1 Tue Oct 1 17:26:20 2002 --- sftp-client.c Tue Nov 5 10:22:52 2002

For all you folks out there using rsync on HP-UX, be warned that HP-UX is still broken with regard to large files. I opened a bug report with HP last year, as described here: http://lists.samba.org/archive/rsync/2004-July/010226.html I've been periodically checking on the status and today I was told that it's been officially filed as a "we won't fix this", citing that the

I'm curious how to go about submitting a suggestion that affects both the original BSD version and the portable release. A few days ago I sent off a BSD-relative patch to openssh at openssh.com. Is this the right thing to do? I didn't hear anything back, but it's only been 3 days, so I'm probably just being too antsy. In the meantime, maybe someone else out there would like to

Good morning! I compiled samba 4.10.8 from source in a slackware 14.2 machine and imported a samba classic domain from an ldap backend. Everything works flawlessly except for a couple of user who are getting their accounts locked out periodically. I'm trying to debug this problem so I modified the smb.conf file of the DC so that it looks like this # Global parameters [global] ??????? dns

Dear rsync-developers, on AIX5.1 with 32-bit kernel one can have large-file support. rsync in principle supports it correctly since the flag _LARGE_FILES is treated correctly in the /usr/include/*.h But there is one point missing, the mkstemp is not opening a large file. So syncing large files crash after 2GB. To avoid this one could either put a #ifdef _LARGE_FILES #undef HAVE_SECURE_MKSTEMP

=================================================================== "Change is such hard work." Billy Crystal =================================================================== Release Announcements ===================== This is is the latest stable release of Samba 3.6. Major enhancements in Samba 3.6.7 include: o Fix resolving our own "Domain Local" groups

=================================================================== "Change is such hard work." Billy Crystal =================================================================== Release Announcements ===================== This is is the latest stable release of Samba 3.6. Major enhancements in Samba 3.6.7 include: o Fix resolving our own "Domain Local" groups

Dear All I've been working at building a file server to provide file sharing for a Windows 2003 Active Directory Domain. Our requirements are for the Windows Server Administrator to be able to create all the users' home folders in the Samba share and apply restrictive permissions. Ie. User joe, //samba/joe$ or //samba/share/joe (Dfs), with permissions for only the user "joe"

=================================================================== "Information's pretty thin stuff unless mixed with experience." Clarence Day ================================================================== Release Announcements ===================== This is the latest stable release of Samba 3.5. Major enhancements in Samba 3.5.16 include: o Fix possible

=================================================================== "Information's pretty thin stuff unless mixed with experience." Clarence Day ================================================================== Release Announcements ===================== This is the latest stable release of Samba 3.5. Major enhancements in Samba 3.5.16 include: o Fix possible