similar to: --fake-super locally?

I have 4 systems and each one of them has a partition I'd like to be remotely accessible on the other 3 systems. In other words System1 has Partition1. Systems 2,3,4 should be able to remotely mount Partition1 from System1. Also System2 has Partition2. Then systems 1,3,4 should be able to remotely mount Partition2 from System2 and so on. I tried NFS and it works but only in the ideal

Greetings! I am working with Lustre-2.1.2 on RHEL 6.2. First I configured it using the standard defaults over TCP/IP. Everything worked very nicely usnig a real, static --mgsnode=a.b.c.x value which was the actual IP of the MGS/MDS system1 node. I am now trying to integrate it with Pacemaker-1.1.7. I believe I have most of the set-up completed with a particular exception. The "lctl

Hi, Compiled openssh3.1p1 by adding '-DINET6' flag to compile line to enable it to be installed on our ipv6 systems. No other code change was done to openssh. Installed it on two ipv6 systems and two ipv4 systems. Whenerer the server is an ipv4 system, ssh client seems to establish connection but it terminates immediately after printing motd message. Here is the typical failure

hi all I have a samba pdc with ldap backed, samba version being 3.0.21c, and openldap 2.3.19. All clients get ip through dhcp and dynamically updates dns also The problem i am facing is from a windows 2000 client if i go to run and browse another system it connects to some other system for example from START-> RUN->\\system1 , it will open some other system say system2 when i ping to

hello all i,m newbie in asterisk and now want to sip and h323 connection. this is my scenario: phone(ext100)--->freepbx---sip--->system1---H323--->system2--->freepbx--->phone(ext200) when i call 100 from 200, every thing is ok and phone is ringing but when i call 200 from 100, it says "service unavailable". i debug asterisk in my system 2 and see below message:

I am sure this is not a problem, but more of a "can we do this" question. We are using Samba Version 2.0.6 and my problem is this: We have one Samba server for a site, we NFS mount filesystems from various other machines to the Samba server, we then create a directory on the Samba server and then create links under that directory to each of the mounted filesystems we want to share.

https://bugzilla.samba.org/show_bug.cgi?id=3299 Summary: rsync: now replaces non-ASCII character with numerical values Product: rsync Version: 2.6.6 Platform: Other URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=307242 OS/Version: Linux Status: NEW Severity: major Priority:

I am on rsync version 3.2.7 protocol version 31, currently on an Arch Linux. The following seems I would expect to copy the contents of 'a' to 'c', based on my understanding of the the advice of `man rsync`: ----- mkdir a b c touch a/hello rsync -M--fake-super -a a/ b/ rsync --super -M--fake-super -a b/ c/ ----- Instead I see 'c' unchanged, and a garbage directory

Hi all, I need to know the details of "save transfer" command using rsync. What is the purpose of using this command. Can we save only the diffs of files using this command? Does it works on stand alone system? Please give me the syntax this command for stand alone system as i want to back up of one directory to another directory(these may be in different partition of hard disk).

On Tue 08 Apr 2025, Graham Leggett via rsync wrote: > > I have a backup that was created with --fake-super that I need to restore to a fresh partition on the same machine as the backup (source and destination on the same machine). > > The docs describe how --fake-super is used to make the backup, but none of the docs describe how you do the reverse and restore. The manpage says:

For your situation I think you should use both --fake-super and -M--super because reading the manual it says: "For a local copy, this option affects both the source and the destination. If you wish a local copy to enable this option just for the destination files, specify -M--fake-super. If you wish a local copy to enable this option just for the source files, combine --fake-super with

Hi all, I have a backup that was created with --fake-super that I need to restore to a fresh partition on the same machine as the backup (source and destination on the same machine). The docs describe how --fake-super is used to make the backup, but none of the docs describe how you do the reverse and restore. Google is hallucinating some nonsense, so that's a dead end. Can anyone confirm

On 08 Apr 2025, at 10:04, Paul Slootman via rsync <rsync at lists.samba.org> wrote: >> I have a backup that was created with --fake-super that I need to restore to a fresh partition on the same machine as the backup (source and destination on the same machine). >> >> The docs describe how --fake-super is used to make the backup, but none of the docs describe how you do

rsync --perms -M--fake-super src dst For me, this command means that rsync should save the original perms in the xattr, and leave the real file mode to the umask default. Currently it also modifies the real file mode, and there is no way to store something different in the xattr. According to an old bug report that I found, more people would like --fake-super to be a complete attribute

Hi all. I long time discover strange to me behavior. If I add --fake-super option on both sides rsync start always set owner and group of symlink. What interesting there no error, but it done each time as it has been changed. Simple reproduce: $ mkdir rsync.symlinks $ echo 'file content' > rsync.symlinks/file.itself $ ln -s file.itself rsync.symlinks/file.symlink Then try to transfer

https://bugzilla.samba.org/show_bug.cgi?id=7112 Summary: --fake-super should use default permissions for real files Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned at samba.org

Thank you for the feedback, I'm glad to see that different people see the issue differently. As a followup question, what would you expect this to do: rsync --perms --chmod g+rX -M--fake-super src dst I would expect it to store the original permissions in the xattr, while modifying the real file mode according to the chmod. On Thursday, March 12, 2020 6:06:34 PM CET, Kevin Korb via rsync

Hello, As i cannot get 3.0.0pre5 to work in my environment (throwing crazy errors which i've posted previously), i would like to revert to 2.6.9 . Of course, the reason i tried to use v3 in the first place was for the acl, xattr, and fake-super options - which, evidently, can be enabled under 2.6.9, as per the following sources: http://lists.samba.org/archive/rsync/2007-February/017218.html

https://bugzilla.samba.org/show_bug.cgi?id=12820 Bug ID: 12820 Summary: rsync always try change owner and group of symlink in --fake-super mode Product: rsync Version: 3.0.9 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core

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