mirror of
https://gitlab.freedesktop.org/dbus/dbus.git
synced 2026-01-31 08:40:31 +01:00
read-only mirror of https://gitlab.freedesktop.org/dbus/dbus
5e948ff7cd
Patch from Timo Hoenig <thoenig@suse.de>.
* bus/bus.c: I've recently investigated why the automatic reload
of configuration files does not work as expected.
Currently, reloading configuration files does only work when
running dbus-daemon with --nodaemon. If we are running as daemon
we're hitting a dnotify bug once we fork the process.
We're initializing the dnotify fds before calling fork(). Once
the child process forked it does still have the fds (and they
still show up in /proc/`pidof dbus-daemon`/fd/) but we're not
getting SIGIO as changes are made to the configuration files.
The attached patch moves the initialization of the dnotify fds to
process_config_postinit(). This is safe for all current code
paths and solves the dnotify disfunction. If we're running
dbus-daemon as daemon the fds for dnotify are now being
initialized after fork() for the child process.
* configure.in: The current configure.in check for dnotify probes
'x$target_os' for being 'xlinux-gnu'. I've changed the check to
match for 'xlinux', too. Additionally I have adapted the configure
option's style to match with the others.
|
||
|---|---|---|
| bus | ||
| dbus | ||
| doc | ||
| gcj | ||
| glib | ||
| mono | ||
| python | ||
| qt | ||
| qt3 | ||
| test | ||
| tools | ||
| .cvsignore | ||
| acinclude.m4 | ||
| AUTHORS | ||
| autogen.sh | ||
| ChangeLog | ||
| configure.in | ||
| COPYING | ||
| dbus-1.pc.in | ||
| dbus-glib-1.pc.in | ||
| dbus-sharp.pc.in | ||
| Doxyfile.in | ||
| HACKING | ||
| INSTALL | ||
| Makefile.am | ||
| Makefile.cvs | ||
| NEWS | ||
| README | ||
| update-dbus-docs.sh | ||
D-BUS is a simple IPC library based on messages. See also the file HACKING for notes of interest to developers working on D-BUS. See http://www.freedesktop.org/software/dbus/ for lots of documentation, mailing lists, etc. Note === A core concept of the D-BUS implementation is that "libdbus" is intended to be a low-level API, similar to Xlib. Most programmers are intended to use the bindings to GLib, Qt, Python, Mono, Java, or whatever. These bindings have varying levels of completeness. Configuration flags === These are the dbus-specific configuration flags that can be given to the ./configure program. --enable-qt enable Qt-friendly client library --enable-glib enable GLib-friendly client library --enable-mono enable mono bindings --enable-mono-docs build mono documentation (requires monodoc) --enable-tests enable unit test code --enable-ansi enable -ansi -pedantic gcc flags --enable-verbose-mode support verbose debug mode --enable-asserts include assertion checks --enable-checks include sanity checks on public API --enable-docs build documentation (requires Doxygen and jade) --enable-gcov compile with coverage profiling instrumentation (gcc only) --enable-python build python bindings (reqires Pyrex >= 0.9) --with-xml=libxml/expat XML library to use --with-init-scripts=redhat Style of init scripts to install --with-session-socket-dir=dirname Where to put sockets for the per-login-session message bus --with-test-socket-dir=dirname Where to put sockets for make check --with-system-pid-file=pidfile PID file for systemwide daemon --with-system-socket=filename UNIX domain socket for systemwide daemon API/ABI Policy === D-BUS API/ABI and protocol necessarily remain in flux until we are sure it will meet the various needs it's intended to meet. This means we need to see some significant sample usage in the contexts of GNOME, KDE, desktop applications, and systemwide uses such as print queue monitoring, hotplug events, or whatever. We need the flexibility to incorporate feedback from this sample usage. Once we feel confident in the protocol and the API, we will release a version 1.0. At that point, the intent is: - The protocol will never be broken again; any message bus should work with any client forever. However, extensions are possible where the protocol is extensible. - If the library API is modified incompatibly, we will rename it as in http://ometer.com/parallel.html - in other words, it will always be possible to compile against and use the older API, and apps will always get the API they expect. Until 1.0 is released, feedback that requires API changes may be incorporated into D-BUS. This may break the API, the ABI, the protocol, or all three. To avoid a huge soname, the plan is to increment the soname only between official stable releases, not with every development snapshot. Versions numbered 0.x are considered development snapshots. Until 1.0 is released, you have to define -DDBUS_API_SUBJECT_TO_CHANGE just as a safety check to be sure everyone is aware of this API/ABI policy and has the right expectations. We do need people to test the APIs, so please do use the development snapshots of D-BUS. They are intended to work and we do actively address bugs. However, if you're shipping a commercial binary-only application that needs to keep running on M future versions of N operating systems, you might want to include your own copy of D-BUS rather than relying on the installed copy, for example.