Apples iCloud är en utmärkt tjänst för att synkronisera information mellan dina Mac-datorer men den täcker inte allt – Mail, iCal, Addressbook och några fler program och funktioner kan du synlkronisera – men inte allt.
Ska du synkronisera annan information så är en smidig lösning programmet Chronosync.
Chronosync är ett mycket enkelt program att konfigurera. Du klickar dig fram till det som ska synkroniseras – du klickar dig fram dit informationen ska, sparar och sedan är det klart.
Du väljer alltså den folder där informationen finns och sedan dit informationen ska. Förslagsvis sparar du sedan din synkning med ett lätt indentifierbart namn (Firefox, iTunes).
Nästa steg är att samla dina synkningar i en synkronisering – en container. Det är en lista, en samling på de synkroniseringar som du har sparat. Sen är det klart.
Du kan köra en container eller en synkronisering manuellt, atomatiskt eller så snart en enhet ansluts – det väljer du.
Chronosync är det program jag använder för kompletterande synkroniseringar och ett tag var det ett program som kördes dagligen, morgon och kväll. Numera behöver jag det inte riktigt lika ofta men det finns kvar i min Mac och det gör fortfarande stor nytta.
- Added more intelligence to the Analyze Panel in an effort to reduce/eliminate unnecessary refreshes.
- Posting entries to a task document’s log during a synchronization is now less thread intensive.
- A ‘bootable’ trigger mode will now enable the EA and ACL variable attribute triggers, but only if both targets support ‘ExtendedInfoCollection’ (i.e., not for connections to old versions of ChronoAgent).
- Implemented an alternate technique for aggregating package files that is much faster on APFS file systems. We now use optimal package aggregation techniques depending on whether we are accessing an APFS or HFS filesystem.
- Internally, all timestamp manipulations and comparisons are done with sub-second precision. The UI still floors to the nearest second, however.
- The Scheduled Tasks database is now loaded and instantiated in a background thread. If you have a large schedule and/or slower computer, ChronoSync will launch faster but you’ll see a delay before scheduled entries appear.
- The filesystem validation logic employed when scanning the contents of folders will now try to adapt to inconsistencies detected in the file system rather than immediately throwing an error. This is because High Sierra is reporting a lot of inconsistencies, especially with SMB mounted file servers.
- If package dissection is OFF, maintaining an archive which contains package files is now much more efficient. Depending on the nature of your sync/backup task, this could yield a significant performance improvement.
- Added the ‘Post more detailed information to the log’ checkbox to the Validator UI. This determines whether or not detailed info will be posted about mismatches. This used to be controlled by the Synchronizer’s equivalent property but now you can control the behavior independently.
- Now prevents the system from sleeping when restoring or deleting a batch of files in the Analyze Panel.
- The process of connecting to target file managers in a scheduled sync (one that runs without a user interface) is now more streamlined and efficient.
- Added new Chinese and Paris endpoints to the Amazon S3 Connection Profile Editor.
- When creating a folder as part of a sync operation, we now wrap the operation in a compound task.
- When the system wakes from sleep, we added logic in an attempt to thwart the problem where, sometimes, the system wakes from sleep for a scheduled sync, but then goes back to sleep before the sync can be started.
- Reworked the 65 second wake assertion we create after invoking a scheduled sync so that it asserts user activity during that time frame if wake-to-sync is enabled.
- Added additional operations that generate diagnostics if schedulerDebug is enabled.
- The application’s scheduler and scheduled items manager now waits for the background scheduler to be launched before starting themselves up (but won’t wait more than 5 seconds).
- When the system wakes from sleep, we now attempt to schedule the next system wake event. This is an attempt to thwart the problem where a system may stop sending us sleep notifications before putting the system to sleep.
- We now schedule a wake event whenever a change is detected in the scheduled items database, the WakeToSync preference is enabled, or the scheduler is turned ON/RESUMED. We also remove all of our scheduled wake events whenever the WakeToSync preference is disabled, or the scheduler is turned OFF/SUSPENDED.
- Implemented a scheme whereby a deadlock in the coordinated read/write of the scheduler database can be broken, thereby disabling the coordinated read-write system. The deadlock breaks after 15 seconds and an error message will be posted to the ChronoSync-Console.log or ChronoSync-Scheduler-Console.log.
- Tweaked the heartbeat logic so that if it has been over 100 seconds since we last checked the schedule, we treat it as if it were an awake-from-sleep event.
- We now declare user activity at the beginning and end of a scheduled sync.
- /private/var/run and /private/var/tmp are no longer content- blacklisted for bootable backups.
- /private/var/vm is now content-blacklisted for bootable backups.
- Added logic to the bootable bless process that ensure /private/ var/vm exists on the destination.
- Added logic to the bootable synchronizer that will only ‘touch’ the system extension folders if .kext were actually copied/deleted by the sync. This triggers a rebuild of the kext caches.
- The Bootable Backup assistant now enables auto-mount for the destination device in all instances. It used to only do this if it was formatted as an encrypted volume by the assistant.
- Deleting a .dylib file is now considered ‘copying’ one, so the dylib caches will get rebuilt at the end of a bootable backup.
- Added initial set of console messages that get generated when synchronizing the APFS Recovery partition fails.
- When synchronizing the Recovery volume as part of an APFS bootable backup, we now dump the Recovery synchronizer’s log to the console if any errors were generated.
- Added diagnostic messages that get generated when preparing/ refreshing an APFS Preboot volume.
- If our initial manual prep of the Preboot volume fails, we now try to call updatePreboot to see if it can prep the volume. Previously, we only called updatePreboot after our manual prep succeeded.
- Added logic to make sure the destination Preboot volume is dismounted after calling the updatePreboot utility because that utility has a tendency to leave it mounted if it produces an error.
- All files and folders created while constructing an APFS Preboot volume are now owned by root:wheel.
- When refreshing an APFS Preboot volume, we now completely delete the /var/db folder in the volume’s Preboot container and let the upodatePreboot utility rebuild it from scratch.
- Modified the Bootable-Backup Recovery volume refresh logic to deal with situations where the source and destination volumes reside within the same APFS container.
- Added a mechanism whereby the maximum number of pooled command sessions is limited by the maxPooledSessions property.
- The prepareToSync method now sets the maxPooledSessions property (if supported) of the target file manager based on the maximum number of concurrent operations plus two.
- Added logic so that if the MIME type returned by the OS does not conform to “type/subtype”, the default MIME type (typically “binary/octet-stream”) is used as the result.
- Reduced the rate of update checks from the ChronoSync Scheduler to once every 24 hours (from once every 12). Our update-check server will be thankful.
- Changed the animation style of the ChronoSync Organizer window to ‘none’. Having it ‘zoom’ open all the time was deemed annoying.
- Added a 15 second wake assertion at application startup.
- We now explicitly set the NSAppSleepDisabled = YES application preference setting when launching the main ChronoSync application.
- Enhanced the DocumentRef’s ‘verify’ method (used by ChronoSync Organizer) so that changes to the ‘displayName’ property are made on the main thread. This is in response to some messages about modifying the auto-layout engine on a background thread that were observed in customer-supplied logs, even though this has never been witnessed.
- Added logic to the SyncTarget’s setFileTimestamps:atPath: method which will use an alternate API for setting creation and modification date if the item resides on a non-AFP file server while running High Sierra (or later). This method is mainly used on folders.
- Added more FMAudit diagnostics to the createFileNamed:inFolder:attributes:flags:newFileRef: method to try and shed light on mysterious permission errors.
- We now redirect stdout to our private log files in addition to stderr.
- Fixed a bug in the Remote Target Selector whereby folder contents presented to the user were not being sorted.
- Hardened some code in the remote target selector UI to reduce the possibility of exceptions getting raised.
- Fixed a validator bug whereby sockets and devices were being included in orphan counts.
- Fixed a bug in the Validator whereby if the user aborted a validation, the file that was presently being compared would get reported as being mismatched. That could cause confusion with the user.
- Fixed a bug in the Validator whereby it would always skip invisible items if Ignore Invisibles was enabled. It really should only skip them if the *source* item is invisible. If it is a bidirectional sync, it should only skip if *both* items are invisible. Otherwise, it could be a mismatch and should be reported.
- Fixed a bug in the Validator whereby the ‘Skip Aliases’ setting was being ignored when comparing the contents of file packages.
- We now clear the package aggregation cache of both target file managers before running a validation.
- Fixed a relatively rare problem which can occur when working off a bootable backup of a system which had ChronoSync installed, and the default document template contains target specifications for volumes that are still online.
- Fixed some bugs related to the mount-check performed prior to any mass file deletions (and periodically during a sync). The bugs would a) lead to ‘false positives’ meaning some file servers could erroneously have dismounts detected, and b) when such a dismount was detected, the error message was extremely unhelpful.
- Fixed a bug whereby, sometimes, authenticating for admin access would cause the Scheduled Tasks Manager window to stay hidden after authentication.
- When moving a file to an archive, we now have an exception handler to catch any exception raised in the process of enumerating a folder in the archive. It will now generate an error rather than throwing an unhandled exception.
- Fixed a bug whereby having the “Don’t create empty folders” setting enabled and running a Trial Sync would skip any folders that need deletion or attribute-only syncs.
- Fixed a bug whereby the display of Roll Back Errors was not interpreting the temporary pre-determination value that was set by previous invocations of the routine which would lead to it being interpreted as the status flags for other roll back warnings.
- Fixed a bug whereby in some cases, posting a verbose log message about file deletion would only show the filename instead of the relative path.
- Fixed a bug whereby some systems mis-report information about running processes and this was confusing ChronoSync into believing that ‘Admin Access’ was not available. The result was an inability to choose “Mounted Volumes (Admin Access)” and might also be the cause of nagging Keychain prompts that some users have reported.
- Fixed a bug when performing a coordinated load of the scheduler database whereby we were briefly referencing a released object (both in ChronoSync and ChronoSync Scheduler).
- Fixed a bug when performing a coordinated load of the Connection Profiles data store whereby we were briefly referencing a disposed object.
- Fixed a bug whereby agent connections (including ‘Admin Access’) that support command pooling were creating superfluous, ‘dead’ command sessions during initial connection and whenever the command session pool filled up.
- Fixed a bug whereby the ChronoSync Scheduler’s system menu could get ‘stuck’ displaying the last frame of an animation. The frame would remain until the user interacted with the menu or another scheduled sync caused it to snap out of the stuck state.
- Fixed a bug whereby it was possible that a popover window would get released before it had fully dismissed. This tended to cause crashes on some systems (mostly 10.11, it seems).
- We now delete the ChronoAgent port semaphore file on the destination (if it exists) during the bless phase of a bootable backup. This should eliminate the ‘Abnormal Startup’ warning that ChronoAgent will present when you boot off the destination.
- Intel, 64-bit processor
- OS X 10.10 or later