{"version":"2.1.282","anchor":"dir-sync-for-attached-clones-files-stay-on-the-peer-and-co","canonical_anchor":"dir-sync-for-attached-clones-files-stay-on-the-peer-and-co","heading":"Directory sync handles attached clones differently","tier":"notice","area":"File Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/dir-sync-for-attached-clones-files-stay-on-the-peer-and-co","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Directory sync handles attached clones differently\n\nFor attached clones, directory sync now leaves files on the other machine and waits on a switch before going ahead\n\n**Unclear.** What controls the switch, and whether it is a remote setting, is not known.\n\n**What**\n\nDirectory sync can work from an attached clone, a copy of a repository linked in from elsewhere. For these sources it now treats the other machine as keeping the files, and before syncing it checks a switch: unless that switch reads \"on\", sync reports that it is switched off. Shutdown now also records whether it was interrupted in the middle of sending changes.\n\n**Why**\n\nIn practice, syncing an attached clone now depends on that switch being on, so it may do nothing until the switch is turned on.\n\n- Area: File Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}