osync | robust two way file sync script | Data Processing library
kandi X-RAY | osync Summary
kandi X-RAY | osync Summary
osync is a Shell library typically used in Data Processing applications. osync has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.
osync provides the following capabilities. osync is a stateful synchronizer. This means it's agentless and doesn't have to monitor files for changes. Instead, it compares replica file lists between two runs. A full run takes about 2 seconds on a local-local replication and about 7 seconds on a local-remote replication. Disabling some features file like attributes preservation and disk space checks may speed up execution. osync uses a initiator / target sync schema. It can sync local to local or local to remote directories. By definition, initiator replica is always a local directory on the system osync runs on. osync uses pidlocks to prevent multiple concurrent sync processes on/to the same initiator / target replica. You may launch concurrent sync processes on the same system but as long as the replicas to synchronize are different. Multiple osync tasks may be launched sequentially by osync osync-batch tool. Currently, it has been tested on CentOS 5.x, 6.x, 7.x, Fedora 22-25, Debian 6-8, Linux Mint 14-18, Ubuntu 12.04-12.10, FreeBSD 8.3-11, Mac OS X, QTS 4.5.1(x86) and pfSense 2.3.x. Microsoft Windows is supported via MSYS or Cygwin and now via Windows 10 bash. Android support works via Termux. Some users also have successfully used osync on Gentoo and created an openRC init scriptt for it.
osync provides the following capabilities. osync is a stateful synchronizer. This means it's agentless and doesn't have to monitor files for changes. Instead, it compares replica file lists between two runs. A full run takes about 2 seconds on a local-local replication and about 7 seconds on a local-remote replication. Disabling some features file like attributes preservation and disk space checks may speed up execution. osync uses a initiator / target sync schema. It can sync local to local or local to remote directories. By definition, initiator replica is always a local directory on the system osync runs on. osync uses pidlocks to prevent multiple concurrent sync processes on/to the same initiator / target replica. You may launch concurrent sync processes on the same system but as long as the replicas to synchronize are different. Multiple osync tasks may be launched sequentially by osync osync-batch tool. Currently, it has been tested on CentOS 5.x, 6.x, 7.x, Fedora 22-25, Debian 6-8, Linux Mint 14-18, Ubuntu 12.04-12.10, FreeBSD 8.3-11, Mac OS X, QTS 4.5.1(x86) and pfSense 2.3.x. Microsoft Windows is supported via MSYS or Cygwin and now via Windows 10 bash. Android support works via Termux. Some users also have successfully used osync on Gentoo and created an openRC init scriptt for it.
Support
Quality
Security
License
Reuse
Support
osync has a medium active ecosystem.
It has 863 star(s) with 90 fork(s). There are 35 watchers for this library.
It had no major release in the last 12 months.
There are 38 open issues and 153 have been closed. On average issues are closed in 129 days. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of osync is v1.3-rc3
Quality
osync has no bugs reported.
Security
osync has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
License
osync is licensed under the BSD-3-Clause License. This license is Permissive.
Permissive licenses have the least restrictions, and you can use them in most projects.
Reuse
osync releases are available to install and integrate.
Installation instructions, examples and code snippets are available.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of osync
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of osync
osync Key Features
No Key Features are available at this moment for osync.
osync Examples and Code Snippets
No Code Snippets are available at this moment for osync.
Community Discussions
Trending Discussions on osync
QUESTION
Cleanup a path list in bash, removing all children paths (subdirectories)
Asked 2020-Jun-30 at 10:50
I have a file containing a list of paths like the following:
...ANSWER
Answered 2020-Jun-30 at 09:00You need two while loops. The outer while loop reads the base paths. And the inner while loops reads the lines to drop.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install osync
osync has been designed to not delete any data, but rather make backups of conflictual files or soft deletes. Nevertheless, you should always have a neat backup of your data before trying a new sync tool. You may get osync on github (stable or latest dev snapshot) or on the author's site (stable version) Getting osync via author's site on https://www.netpower.fr/osync. Getting osync via github (remove the -b "stable" if you want latest dev snapshot). Installer script accepts some parameters for automation. Launch install.sh --help for options. There is also a RPM file that should fit RHEL/CentOS/Fedora and basically any RPM based distro, see the github release. Please note that RPM files will install osync to /usr/bin instead of /usr/local/bin in order to enforce good practices. osync will install itself to /usr/local/bin and an example configuration file will be installed to /etc/osync. osync needs to run with bash shell. Using any other shell will most probably result in errors. If bash is not your default shell, you may invoke it using. On *BSD and BusyBox, be sure to have bash installed.
Since osync v1.1 the config file format has changed in semantics and adds new config options. Also, master is now called initiator and slave is now called target. osync v1.2 also added multiple new configuration options. You can upgrade all v1.0x-v1.2-dev config files by running the upgrade script. The script will backup your config file, update it's content and try to connect to initiator and target replicas to update the state dir.
Since osync v1.1 the config file format has changed in semantics and adds new config options. Also, master is now called initiator and slave is now called target. osync v1.2 also added multiple new configuration options. You can upgrade all v1.0x-v1.2-dev config files by running the upgrade script. The script will backup your config file, update it's content and try to connect to initiator and target replicas to update the state dir.
Support
All kind of contribs are welcome. When submitting a PR, please be sure to modify files in dev directory (dev/n_osync.sh, dev/ofunctions.sh, dev/common_install.sh etc) as most of the main files are generated via merge.sh. When testing your contribs, generate files via merge.sh or use bootstrap.sh which generates a temporary version of n_osync.sh with all includes. Unit tests are run by travis on every PR, but you may also run them manually which adds some tests that travis can't do, via dev/tests/run_tests.sh SSH port can be changed on the fly via environment variable SSH_PORT, eg: SSH_PORT=2222 dev/tests/run_tests.sh. Consider reading CODING_CONVENTIONS.TXT before submitting a patch.
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page