File: README.dbus

package info (click to toggle)
backup-manager 0.7.9-3
  • links: PTS, VCS
  • area: main
  • in suites: squeeze
  • size: 1,400 kB
  • ctags: 209
  • sloc: sh: 3,584; perl: 1,002; makefile: 210
file content (35 lines) | stat: -rw-r--r-- 1,234 bytes parent folder | download | duplicates (7)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
Warning: These interfaces are still experimental and are subject to
change.

backup-manager supports reporting its activity over dbus. Programs
wanting to be notified should listen to these messages of the
org.backupmanager.BackupManager interface :

* ProgressNotify (int32 percentage, string label)
* EventNotify (string event_name, string argument)
* LogMessageNotify (string level, string message)

Depending on who launched backup-manager (root or user), these messages
are sent from the following bus objects :
* /org/backupmanager/instance/SystemInstance of the system bus if
  launched by root.
* /org/backupmanager/instance/UserInstance/${USERNAME} of the user
  session bus if launched by a regular user.

If the dbus-send program is not in $PATH, or if the selected bus is
unreachable, backup-manager should operate as normal, just not
reporting its activity.

To test, just launch, in two different terminals for better
readability:

* as root :
 # dbus-monitor --system \
      "type='signal',interface='org.backupmanager.BackupManager'"
 # backup-manager [...] # as usual

* or as a user :
 $ dbus-monitor --session \
      "type='signal',interface='org.backupmanager.BackupManager'"
 $ backup-manager [...] # as usual