diff --git a/DBus-service.md b/DBus-service.md index ad293fd..1af2e2b 100644 --- a/DBus-service.md +++ b/DBus-service.md @@ -26,21 +26,21 @@ Then RESTART YOUR MACHINE (I dont know why this is needed, but it is needed for To run on the system bus you need to take some additional steps. It’s advisable to run signal-cli as a separate unix user, the following steps assume you created a user named *signal-cli*. To run a service on the system bus, a config file is needed to allow the signal-cli user to take a name on the system bus. An example config file can be found in `data/org.asamk.Signal.conf`. This file also configures that any user can talk with the signal-cli daemon. -The `data/org.asamk.Signal.service` and `data/signal.service` files configure a dbus activated systemd service for signal-cli, so the service is automatically started when the dbus service is requested. +The `data/org.asamk.Signal.service` and `data/signal-cli.service` files configure a dbus activated systemd service for signal-cli, so the service is automatically started when the dbus service is requested. These steps, executed as root, should work on all distributions using systemd. ```bash cp data/org.asamk.Signal.conf /etc/dbus-1/system.d/ cp data/org.asamk.Signal.service /usr/share/dbus-1/system-services/ -cp data/signal.service /etc/systemd/system/ -sed -i -e "s|%dir%||" -e "s|%number%||" /etc/systemd/system/signal.service +cp data/signal-cli.service /etc/systemd/system/ +sed -i -e "s|%dir%||" /etc/systemd/system/signal-cli.service systemctl daemon-reload -systemctl enable signal.service +systemctl enable signal-cli.service systemctl reload dbus.service ``` -Mind the fact that signal.service executes the signal-cli with "--config /var/lib/signal-cli". +Mind the fact that signal-cli.service executes the signal-cli with "--config /var/lib/signal-cli". If you registered with user signal-cli, remove the config option. Make sure to use "--dbus-system" with the send command, the service will be autostarted by dbus the first time it is requested.