Opened 12 years ago
Closed 12 years ago
#36411 closed defect (invalid)
dbus startup automation not explained
Reported by: | wd11@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.1.2 |
Keywords: | Cc: | ||
Port: | dbus |
Description (last modified by pixilla (Bradley Giesbrecht))
$ port notes dbus dbus has the following notes: ############################################################################ # Startup items have been generated that will aid in # starting dbus with launchd. They are disabled # by default. Execute the following command to start them, # and to cause them to launch at startup: # # sudo launchctl load -w /Library/LaunchDaemons/org.freedesktop.dbus-system.plist # launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist ############################################################################
It remains to be be explained somewhere, *how* an automatic launch of these commands should/can be caused at startup.
Change History (3)
comment:1 Changed 12 years ago by pixilla (Bradley Giesbrecht)
comment:2 Changed 12 years ago by pixilla (Bradley Giesbrecht)
Description: | modified (diff) |
---|
Please use wiki formatting and cc the ports maintainer.
comment:3 Changed 12 years ago by pixilla (Bradley Giesbrecht)
Resolution: | → invalid |
---|---|
Status: | new → closed |
Research launchctl, launchd and launchd plists for an understanding of how they function.
Note: See
TracTickets for help on using
tickets.
Read: