1MISSION-CONTROL-5(8)            D-Bus services            MISSION-CONTROL-5(8)
2
3
4

NAME

6       mission-control-5 - Telepathy account manager/chanel dispatcher
7

SYNOPSIS

9       /usr/libexec/mission-control-5
10

DESCRIPTION

12       Mission  Control  5 implements the AccountManager and ChannelDispatcher
13       services described  in  the  Telepathy  D-Bus  specification,  allowing
14       clients  like empathy(1) to store account details, connect to accounts,
15       request communication channels, and have channels dispatched to them.
16
17       It is a D-Bus service which runs on the session bus, and should usually
18       be started automatically by D-Bus activation. However, it might be use‐
19       ful to start it manually for debugging.
20

OPTIONS

22       There are no command-line options.
23

ENVIRONMENT

25       MC_DEBUG=all or MC_DEBUG=category[,category...]
26              May be set to "all" for full debug output from  Mission  Control
27              and  telepathy-glib,  or  various  undocumented  category  names
28              (which may change from release to release) to filter the output.
29              See  Mission  Control  and  telepathy-glib  source  code for the
30              available categories.
31
32       MC_DEBUG=level
33              Set a numeric debug level for Mission Control  itself  (but  not
34              telepathy-glib).   Level  0 logs nothing, level 1 logs most mes‐
35              sages, and level 2 logs all messages.
36
37       MC_TP_DEBUG=type
38              May be set to "all" for full debug output  from  telepathy-glib,
39              or  various  undocumented options (which may change from telepa‐
40              thy-glib release to release) to filter the output.  See  telepa‐
41              thy-glib source code for the available options.
42

SEE ALSO

44       http://telepathy.freedesktop.org/
45
46
47
48Telepathy                          July 2009              MISSION-CONTROL-5(8)