Home | History | Annotate | Download | only in tools

Lines Matching full:autolaunch

10 .B dbus-launch [\-\-version] [\-\-sh-syntax] [\-\-csh-syntax] [\-\-auto-syntax] [\-\-exit-with-session] [\-\-autolaunch=MACHINEID] [\-\-config-file=FILENAME] [PROGRAM] [ARGS...]
84 the --autolaunch option to start up a new session bus or find the
89 Whenever an autolaunch occurs, the application that had to
96 There are two common reasons for autolaunch. One is ssh to a remote
104 The second common reason for autolaunch is an su to another user, and
112 You can always avoid autolaunch by manually setting
113 DBUS_SESSION_BUS_ADDRESS. Autolaunch happens because the default
114 address if none is set is "autolaunch:", so if any other address is
115 set there will be no autolaunch. You can however include autolaunch in
117 DBUS_SESSION_BUS_ADDRESS="something:,autolaunch:" - in that case if
118 the first address doesn't work, processes will autolaunch. (The bus
122 The --autolaunch option is considered an internal implementation
162 .I "--autolaunch=MACHINEID"
166 \-\-exit-with-session option is implied if \-\-autolaunch is given.