mirror of
https://github.com/AsamK/signal-cli
synced 2025-09-01 20:10:39 +00:00
Update README.md
I use a server monitoring solution (Zabbix) and wanted to use signal-cli for notifications. The monitoring solutions can call external scripts in case of problems but obviously uses it's own user to do this. I read about --config in the source and thought, that other people would benefit from this information as well.
This commit is contained in:
parent
1bae3ba6f0
commit
5b57d41791
1 changed files with 6 additions and 0 deletions
|
@ -105,6 +105,12 @@ usage: signal-cli [-h] [-v] [--config CONFIG] [-u USERNAME | --dbus | --dbus-sys
|
|||
|
||||
signal-cli -u USERNAME trust -a NUMBER
|
||||
|
||||
* Set configuration directory
|
||||
|
||||
signal-cli -config=/home/other_user/.config/signal
|
||||
|
||||
This is particularily useful in the case, when you would like to run the signal-cli tool as a different user as the one, that was used to register the account. You should make sure, that the caller can list and read the given directory.
|
||||
|
||||
## DBus service
|
||||
|
||||
signal-cli can run in daemon mode and provides an experimental dbus interface.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue