I have worked on a file in Directory A. There is a file with the same name in directory B which is an older version of that same file. I rsync everything from B to A.

What happens to my work in the file in directory A?

    • WasPentaliveOP
      link
      fedilink
      arrow-up
      4
      ·
      edit-2
      1 year ago

      Thanks - Looking at the man page, It looks like I would want --update in this case as it would cause the newer version to be present in both directories afterward.

        • WasPentaliveOP
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          After a session or two where I have perhaps only worked in A or B alone. I can manually trigger the shell script. Thanks for confirming tho.

  • sportsfork@sopuli.xyz
    link
    fedilink
    arrow-up
    8
    ·
    1 year ago

    there are a gazillion switches to control the behavior. Like, --ignore-existing, to not overwrite any existing files …

  • WasPentaliveOP
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    The actual use case: I have an emulator that uses a directory as the ‘system disk’ of the computer being emulated, but I have one of these on each of two machines. As I make updates I want to have the proper files updated on the other directory so between changes on the two emulators the most recent is synced to the other directory.

    It seems I will need to use 2 rsync commands, one in each direction. Update A from B, then update B from A.

  • Lemmyin@lemmy.nz
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    I have no idea what types of files these are but it could turn out that you should rather use Git and push/pull from both sides which could works better.

    Just a suggestion :)