clsync

USE flags

• apidoc - Provide doxygen generated API docs.
• caps - Use Linux capabilities library to control privilege
• cgroups - Use cgroups to limit /dev access.
• clsync - Build clsync binary. Most likely you want it. However it is possible to build only libclsync without clsync itself.
• cluster - Enable clustering support (allows master-master clsync on multiple hosts). Not fully implemented yet.
• control-socket - Enable AF_UNIX control socket support.
• debug - Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces
• doc - Add extra documentation (API, Javadoc, etc). It is recommended to enable per package instead of globally
• examples - Install examples, usually source code
• extra-debug - Enable extra debugging. This will hurt performance badly. Be ready for tons of output.
• extra-hardened - Enable extra security checks. This will hurt performance.
• gio - Enable GIO for FS monitoring (glib based alternative to inotify interface, not recommended; if both are compiled, may be selected at runtime).
• hardened - Activate default security enhancements for toolchain (gcc, glibc, binutils)
• highload-locks - Allows to use spinlocks for short delays instead of mutexes, but only on SMP systems.
• inotify - Enable inotify filesystem monitoring support
• lto - Build with link time optimization (LTO).
• mhash - Add support for the mhash library
• namespaces - Enable namespaces isolation.
• seccomp - Enable seccomp (secure computing mode) to perform system call filtering at runtime to increase security of programs
• socket-library - Build the control and monitoring socket library: libclsync.
• static-libs - Build static versions of dynamic libraries as well