search for: avax

Hi, I've been attempting to use rsync 3.1.2 to copy files from a macOS 10.12.2 system to an AFP mounted share. The command I'm using is: rsync -avAX -M--fake-super ./testDir ./mnt/testDir/ This works fine and all the extended attributes are copied and readable. I then try to use rsync to copy these files back with: rsync -avAX --fake-super -M--super ./mnt/testDir/ ./testDir2/ This outputs errors such as: rsync: get_xattr_data: lgetxattr(&q...

...be, but then I can't edit it on my system if it is root:named! > Given all of the above, with public key authentication set up, you > could then invoke the following command string from the parent > directory of the backup (/home/rgm/data/htt/httnet/homebase/new/etc): > > rsync -avAX --delete root at 192.168.192.2:/etc/named/ named > rsync -avAX --delete root at 192.168.192.2:/etc/named.conf named.conf In /etc there are 4 named.* files. Do I have to do each separately? > ... and so on > > hth & regards, > > Carl > ____________________________________...

...a backup, you really should consider preserving ACLs and extended attributes (-A -X,) too. Given all of the above, with public key authentication set up, you could then invoke the following command string from the parent directory of the backup (/home/rgm/data/htt/httnet/homebase/new/etc): rsync -avAX --delete root at 192.168.192.2:/etc/named/ named rsync -avAX --delete root at 192.168.192.2:/etc/named.conf named.conf ... and so on hth & regards, Carl

...http://www.socallinuxexpo.org On Tue, Jan 3, 2017 at 7:16 AM, Steven Kilby <stevenkilby2 at gmail.com> wrote: > Hi, > > I've been attempting to use rsync 3.1.2 to copy files from a macOS 10.12.2 > system to an AFP mounted share. The command I'm using is: > > rsync -avAX -M--fake-super ./testDir ./mnt/testDir/ > > This works fine and all the extended attributes are copied and readable. > > I then try to use rsync to copy these files back with: > > rsync -avAX --fake-super -M--super ./mnt/testDir/ ./testDir2/ > > This outputs errors such as:...

...tle for a borg backend with pika up front and perhaps the lack of regular use caused me to run: `[admin at server mymachine-home]$ rsync -aAX root at 192.168.1.141:/home/ .` And, after doing what I needed to do with /home on mymachine, I put it all back: `[admin at server mymachine-home]$ rsync -avAX . root at 192.168.1.141:/home/` Only to discover - obviously in hindsight - that I'd failed to run as root and now the whole of /home (appears) to belongs to `admin` (a user that doesn't exist on mymachine). So, my strategy: 1/ Assume that the wrong owner is the only problem thown up by...

...onnect, ftp server ect) and they dont have any problems. Can you give me any advices ? Its happen on diferent physical servers, in diferent companies ... Same problems :(. Thanks for your time :) I use Samba as DC, nothing special in smb.conf, here is what I use: [global] <------>workgroup = AVAX <------>realm = AVAX.LOC <------>netbios name = DC-01 <------>server role = active directory domain controller <------>dns forwarder = 192.168.1.254 <------>allow dns updates = nonsecure <------>load printers = yes nothing more. krb5 configured, DNS worked fine...

Any plane in future to build-in Samba SysVol replication (DFS-R) ? For now we have this workaround at link: https://wiki.samba.org/index.php/Rsync_based_SysVol_replication_workaround

I am trying to rsync the named files under /etc for backup purposes. I tried: rsync -ah --stats --delete -e "ssh -p613 -l root" 192.168.192.2:/etc/name* /home/rgm/data/htt/httnet/homebase/new/etc The stats shows it sees all the files, but only moves the dir /etc/named and the files within it. It does not move the /etc/name* files (like /etc/named.conf). By file count, it is

...- Hash: SHA1 I've compiled rsync 3.0.3 on OSX 10.4 PPC via the plain jane ./configure; make method (no patches). The resulting binary has then been moved to /usr/local/bin/rsync3 and copied to a OSX 10.5.4 Intel client machine as rsync3. I then run the following command: rsync3 -vvv -e ssh -avAX --progress --delete - --rsync-path='/usr/local/bin/rsync3' root@xserver:/Users/portman/Sites/index.html /Volumes/MacHardDisk/Users/portman/Sites/index.html Which results in the following attached log. The entire transfer of data seems to proceed just fine, but it hangs and exits uncleanly...

...different one on the target DC when the target DC is on Debian Bookworm with both samba 4.17.<many> and 4.18.8 . It looks like a different behaviour of rsync that I never saw on Bullseye or before, with many different samba versions over the years. I'm using rsync through ssh with rsync -avAX --delete /var/lib/samba/sysvol dcX:/var/lib/samba The winbind message disappears when adding --numeric-ids so that rsync does not need to use winbind to map from user and group names to Unix UIDs and GIDs. Besides the different rsync version on Bookworm it has to do with the history of my domain:...

Hi all, I know this is kind of an old thread, but I've got some new "developments". And some questions too. Let's see... So, like I said before, my file server is clogging my logs with ../../source3/winbindd/winbindd_getgroups.c:259(winbindd_getgroups_recv) Could not convert sid S-0-0: NT_STATUS_NONE_MAPPED Every 2 seconds. Now, I'm using netdata

https://bugzilla.samba.org/show_bug.cgi?id=5365 Summary: --backup and --xattrs are not compatible Product: rsync Version: 3.0.0 Platform: x86 OS/Version: Other Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: fauthier@free.fr