RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1258868 - [RFE] dbus should reload configuration automatically (inotify)
Summary: [RFE] dbus should reload configuration automatically (inotify)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dbus
Version: 7.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: David King
QA Contact: Desktop QE
URL:
Whiteboard:
: 1308549 (view as bug list)
Depends On:
Blocks: 1218420
TreeView+ depends on / blocked
 
Reported: 2015-09-01 12:30 UTC by Miroslav Vadkerti
Modified: 2019-09-11 17:32 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-11 17:32:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Miroslav Vadkerti 2015-09-01 12:30:13 UTC
Description of problem:
Currently when a new dbus configuration file is added by a newly installed application - dbus must be restarted to take the changes into affect.

Dbus should use inotify to monitor its configuration paths and reload the configuration automatically. For example polkit does this.

Version-Release number of selected component (if applicable):
dbus-1.6.12-13.el7

How reproducible:
100%

Steps to Reproduce:
1. Add new configuration file

Actual results:
Dbus reloads config automatically

Expected results:
Dbus runtime config not changed

Comment 1 Michal Sekletar 2015-09-02 10:56:29 UTC
I don't think this is the right approach. In order for new configuration to take effect daemon must be *explicitly* asked to do so. Config must not be applied right after admin hits save in $EDITOR.

Also note that D-Bus demon supports partial reload of its configuration, man page says following,

"SIGHUP  will cause the D-Bus daemon to PARTIALLY reload its configuration file and to flush its user/group information caches. Some configuration changes would require kicking all apps off the bus; so they will only take effect if you restart the daemon. Policy changes should take effect with SIGHUP."

Comment 2 Miroslav Vadkerti 2016-01-13 08:07:48 UTC
(In reply to Michal Sekletar from comment #1)
> I don't think this is the right approach. In order for new configuration to
> take effect daemon must be *explicitly* asked to do so. Config must not be
> applied right after admin hits save in $EDITOR.

I do not mind if the reload would be explicit.

> 
> Also note that D-Bus demon supports partial reload of its configuration, man
> page says following,

Unfortunately does not work at all for me (I am trying to add a new dbus service file which I do not find a very intrusive operation), see bug 1258865

> 
> "SIGHUP  will cause the D-Bus daemon to PARTIALLY reload its configuration
> file and to flush its user/group information caches. Some configuration
> changes would require kicking all apps off the bus; so they will only take
> effect if you restart the daemon. Policy changes should take effect with
> SIGHUP."

Comment 4 David King 2016-02-16 13:51:49 UTC
*** Bug 1308549 has been marked as a duplicate of this bug. ***

Comment 8 Matthias Clasen 2019-09-11 17:32:29 UTC
D-Bus behaves as documented. We can't just change this behavior.


Note You need to log in before you can comment on or make changes to this bug.