mirror of
https://salsa.debian.org/ha-team/libqb
synced 2026-08-08 20:07:21 +00:00
f950a5d3f8
Use mkdtemp makes sure that IPC files are only visible to the owning (client) process and do not use predictable names outside of that. This is not meant to be the last word on the subject, it's mainly a simple way of making the current libqb more secure. Importantly, it's backwards compatible with an old server. It calls rmdir on the directory created by mkdtemp way too often, but it seems to be the only way to be sure that things get cleaned up on the various types of server/client exit. I'm sure we can come up with something tidier for master but I hope this, or something similar, will be OK for 1.0.x. |
||
|---|---|---|
| .tito | ||
| build-aux | ||
| docs | ||
| examples | ||
| include | ||
| lib | ||
| m4 | ||
| tests | ||
| tools | ||
| .gitignore | ||
| .tito.spec.tmpl | ||
| .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.