Editing DbusScripts
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
Warning: This page is 38 kilobytes long; some browsers may have problems editing pages approaching or longer than 32kb. Please consider breaking the page into smaller sections.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 73: | Line 73: | ||
=== dbus-scripts daemon options === | === dbus-scripts daemon options === | ||
- | ==== | + | ==== System vs. session buses ==== |
- | By default, the dbus-scripts daemon listens on the system message bus, which reports system events but not those from the user session. If you want to access events such as an application being launched, you'll need to configure the daemon to listen to the session bus | + | By default, the dbus-scripts daemon listens on the system message bus, which reports system events but not those from the user session. If you want to access events such as an application being launched, you'll need to configure the daemon to listen to the session bus. You'll probably want to run a second instance of dbus-scripts without breaking the one on the system bus. |
Ignore <code>/etc/init.d/dbus-scripts</code> and <code>/etc/default/dbus-scripts</code> as these would seem to have been superseded by upstart. Make a copy of <code>/etc/event.d/dbus-scripts</code> as <code>/etc/event.d/dbus-scripts-session</code> and edit it so your <code>/etc/event.d/dbus-scripts-session</code> will look like this: | Ignore <code>/etc/init.d/dbus-scripts</code> and <code>/etc/default/dbus-scripts</code> as these would seem to have been superseded by upstart. Make a copy of <code>/etc/event.d/dbus-scripts</code> as <code>/etc/event.d/dbus-scripts-session</code> and edit it so your <code>/etc/event.d/dbus-scripts-session</code> will look like this: |
Learn more about Contributing to the wiki.