mirror of
https://salsa.debian.org/ha-team/libqb
synced 2026-01-11 16:51:28 +00:00
When creating a unix socket it's default gid is that of the parent directory. If the SOCKETDIR is owned by root:wheel with 1777 mode some of the pacemaker daemons end up unable to communicate with one another due to having insufficient permissions on the sockets. This can be fixed by setting the client sockets gid to the primary group of the server socket owner it's attempting to connect to. And, on the server side by setting the gid to the already captured gid stored in the connection info. This ensures that regardless of who owns the socket directory, as long as the applications have r/w access to it they should work. |
||
|---|---|---|
| build-aux | ||
| docs | ||
| examples | ||
| include | ||
| lib | ||
| tests | ||
| tools | ||
| .gitignore | ||
| .travis.yml | ||
| autogen.sh | ||
| check | ||
| coding_style.txt | ||
| configure.ac | ||
| COPYING | ||
| INSTALL | ||
| libqb.spec.in | ||
| Lindent | ||
| Makefile.am | ||
| README.markdown | ||
libqb
What is libqb?
libqb is a library with the primary purpose of providing high-performance, reusable features for client-server architecture, such as logging, tracing, inter-process communication (IPC), and polling.
libqb is not intended to be an all-encompassing library, but instead provide focused APIs that are highly tuned for maximum performance for client-server applications.
For more information, see:
-
You can build it yourself with the following commands:
$ make doxygen $ firefox ./doc/html/index.html
Dependencies
- glib-2.0-devel (If you want to build the glib example code)
- check-devel (If you want to run the tests)
- doxygen and graphviz (If you want to build the doxygen man pages or html manual)
Source Control (GIT)
git clone git://github.com/ClusterLabs/libqb.git
Installing from source
$ ./autogen.sh
$ ./configure
$ make
$ sudo make install
How you can help
If you find this project useful, you may want to consider supporting its future development. There are a number of ways to support the project.
- Test and report issues.
- Help others on the developers@clusterlabs.org mailing list.
- Contribute documentation, examples and test cases.
- Contribute patches.
- Spread the word.
