Chronosync parameter error3/24/2023 We consciously decided to have CS report such problems because a bad symbolic link inside a package is essentially a corrupt file, even though it may just be ‘minimally’ corrupt. It should be noted that Finder ignores bad symbolic links in packages so when copying a package file with a bad synclink, the error goes unreported. To troubleshoot this issue, you can try deleting the troubled symlink(s) and recreating them to see if that resolves the errors in ChronoSync. If the item being referenced exists within the package, then it’s possible the destination file system doesn’t support symbolic links (although that is unlikely). ChronoSyncs Error Handling assistant can modify the error handling behavior of multiple synchronizer tasks at once. You can “Get Info” in Finder and see what item it is referring to. Just expand the package file on Analyze until you find the troubled file being reported. This is very common with code frameworks.Įnable ‘Dissect Packages’ on the Options Panel of your sync document to reveal the symlink(s) in question on the Analyze Panel. ![]() Usually packages will have a self-referencing symlink inside them meaning there’s a symbolic link that references one of the files/folders within the packages. ![]() A ‘bad’ symbolic link would be one that references a file that does not exist. You can access a ChronoAgent-enabled Mac over your local network or even across the country via the Internet. This error is generated by ChronoSync when copying a package file that either has a ‘bad’ symbolic link in it or cannot have the symbolic link recreated on the destination. ChronoAgent is a silent background utility that allows a Mac to accept secure connections from ChronoSync and InterConneX for file transfers, folder synchronization or backups.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |