similar to: [Bug 3253] Feature request - Sync perms/ownership/time etc but with no file transfer

https://bugzilla.samba.org/show_bug.cgi?id=3253 Summary: Feature request - Sync perms/ownership/time etc but with no file transfer Product: rsync Version: 2.6.7 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

https://bugzilla.samba.org/show_bug.cgi?id=6578 Summary: put out skipped dirs files w/ perms and ownership Product: rsync Version: 3.0.5 Platform: All OS/Version: Linux Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: toralf.foerster

Centos 4.3 Hi All: I just shot myself in the foot by change the owner/perms on the contents of the root directory (my bad!!!). I have done a quick compare with a running RHEL3U8 system and think I have every thing back to what it should be except for new directories media and selinux. Can someone out there currently running 4.3 send me an "ls -l" of their root directory so I can make

Back in late March I asked what ownership and permissions Dovecot's own directories and files should have; I have an obsessive nature, and wanted to get things right :(.. On April Fool's Day :), Timo responded: > Dovecot opens pretty much all the configuration etc. files as root > before dropping the privileges. So in general they could all be 0600 > owned by root In my

I have Dovecot2 auth setup to run as user = doveauth group = dovecot configured in, vi conf.d/10-master.conf ... service auth { unix_listener /var/spool/postfix/private/auth { user = postfix group = postfix mode = 0660 } user = doveauth group = dovecot } service auth-worker { user = doveauth group = dovecot } ... When I start Dovecot, ls -al

Hi, Been using rsync for many years but I'm stuck with this problem. I'ts a simplistic backup using rsync from a Windows 2k3 machine to a Linux box out on the 'net, using pre-shared ssh keys. In this case I'm saving, files belonging to various users, using the administrator account on the windows machine and the destination is a normal user account and its home file area.

I'm looking to see of it is practical to have an rsync server run a script after a transfer finishes. I am moving files (python source) from windows (common point of development) to a few linux machines. big problem being owner/group/perms are always wrong and python's module install process is fragile with respect to OGP. Therefore, I want to run a script after transferring a set

https://bugzilla.samba.org/show_bug.cgi?id=6197 Summary: Perms/owner/group modifiers for "show" filters Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

I'm migrating from C7 to C8.? I'm currently using autofs, but alas autofs has been dropped in C8 for the AMD automounter. I have some very ancient knowledge of AMD, I used it when it was first introduced many years ago on Solaris and moved to Sun's automounter when it was introduced. So now it's back to square one. I used automount2amd to convert one of my existing maps,

I have the following script that I am working on #!/bin/bash date=$(date +%F--%T) #ssh parameters user=aquj001 remotehost=qa4app localdir=/home/aquj001/INFENG/scripts remotedir=/home/aquj001/recievingDir.$date linkdest=$(ssh $user@$remotehost /usr/linux/bin/readlink/ /home/aquj001/recievingDir.current) rsync -a --compress --link-dest=$linkdest --out-format='%i %n%L %l %M'

https://bugzilla.mindrot.org/show_bug.cgi?id=3253 Bug ID: 3253 Summary: ssh-keygen man page still lists deprecated key types for -t Product: Portable OpenSSH Version: 8.4p1 Hardware: Other OS: Linux Status: NEW Severity: minor Priority: P5 Component: ssh-keygen

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

I have the following situation: file2 on remote host and file1 on localhost. file1 and file2 are mostly the same. Simply running rsync remotehost:file2 file2 will actually transfer the entire file. But I would like to use the factt that I have local file1 that is mostly similar to file2. I.e. how can I make rsync to use file1 as a reference while transferring file2? (cp file1 file2 locally and

This is frustrating: $ export LIBVIRT_DEFAULT_URI=qemu+ssh://remotehost/session $ virsh list error: failed to connect to the hypervisor error: no valid connection error: Operation not supported: Connecting to session instance without socket path is not supported by the ssh connection driver Has there been any thought given to making this easier? It seems that having a simple helper

We try to run a reliable ssh tunnel vis systemd. This is the unit configuration file: {{{ [Unit] Description=Tunnel For %i After=network.target [Service] User=autossh ExecStart=/usr/bin/ssh -o "ExitOnForwardFailure yes" -o "ServerAliveInterval 60" -N -R 40443:installserver:40443 -R 8080:installserver:8080 ExecStartPre=-/usr/bin/ssh tunnel@%i "for pid in $$(ps -u

Hi ? I put the rsync in cronjob but it won't work ? in root user cron ? */30? * * * *? /home/chloe/rsy.sh >/dev/null 2>&1 ? 1/ why it needs pw when I run this rsy.sh in root? but if I run it in chloe user, it doesn't need pw as I put authoized_key in remote host chloe ? 2/ why this root cronjob is not working? what wrong? I can't see this cron in message ? the rsy.sh is

Hi All! I am puzzled. I am using openssh 5.3p1 on RHEL/CentOS but am seeing the same behaviour for osx and debian: ssh -R xxx:yyy:yyy:yyy remotehost Will effectively drop the first (xxx) argument and result in ssh -R 127.0.0.1:yyy:yyy:yyy remotehost ssh -R yyy:yyy:yyy remotehost I had a look at the source code where apparently all 4 values are ready and handed down to the appropriate

Thanks. This is a bit counter-intuitive to me. So how would you tell rsync to store the original permissions in the xattr, but do not touch the real file mode? On Thursday, March 12, 2020 6:26:18 PM CET, Kevin Korb via rsync wrote: > I would expect that the sending rsync would only send the perms provided > modified by the --chmod. I wouldn't expect the receiver to even know > the

https://bugzilla.samba.org/show_bug.cgi?id=11027 Bug ID: 11027 Summary: Sticky bit not set when using --chmod=D+t alone, without --perms Product: rsync Version: 3.0.9 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee:

https://bugzilla.samba.org/show_bug.cgi?id=9377 Summary: acls ignored when using neither --perms nor --chmod Product: rsync Version: 3.0.9 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: chrysn at fsfe.org