path: ntfy_2.11.0-3/docs/config.md
You can also hot-reload the `log-level` and `log-level-overrides` by sending the `SIGHUP` signal to the process after 
editing the `server.yml` file. You can do so by calling `systemctl reload ntfy` (if ntfy is running inside systemd), 
or by calling `kill -HUP $(pidof ntfy)`. If successful, you'll see something like this:
```


path: ntfy_2.11.0-3/docs/troubleshooting.md
# Only list ntfy logs
adb logcat --pid=$(adb shell pidof -s io.heckel.ntfy)
adb -s 192.168.1.137:39539 logcat --pid=$(adb -s 192.168.1.137:39539 shell pidof -s io.heckel.ntfy)
```


path: ntfy_2.11.0-3/docs/troubleshooting.md
# Only list ntfy logs
adb logcat --pid=$(adb shell pidof -s io.heckel.ntfy)
adb -s 192.168.1.137:39539 logcat --pid=$(adb -s 192.168.1.137:39539 shell pidof -s io.heckel.ntfy)
```


path: ntfy_2.11.0-3/docs/subscribe/cli.md
    ```
=== "Using a `pidof`"
    ```
    $ ntfy pub --wait-pid $(pidof rsync) mytopic | jq .


path: ntfy_2.11.0-3/docs/subscribe/cli.md
=== "Using a `pidof`"
    ```
    $ ntfy pub --wait-pid $(pidof rsync) mytopic | jq .
    {
      "id": "orM6hJKNYkWb",