From None Mon Jan 3 10:29:42 2022 From: None To: op25-dev@lists.osmocom.org Subject: None Date: Mon, 03 Jan 2022 10:29:42 +0000 Message-ID: <164120578294.15306.10350348559223872567.generated@lists> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7426014581262678676==" --===============7426014581262678676== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable support receiving signals from the OS? For example, SIGUSR1 might re-read the list of white-listed talkgroups. We have a countywide fire dispatch talkgroup, plus a number of fireground channels. I'm imagining a simple web interface that would rewrite whitelist.tsv and then send SIGHUP or SIGUSR1 to rx.py so it reloads the configuration. If we don't need to hear the incident on fireground 2, the end-user can easily "nuisance delete" that talkgroup from the web interface. Alternatively, maybe we start with all the fireground channels muted and use the web interface to un-mute the one(s) we want to listen to. --=20 _ | | |-| | |pu http://www.spfld.com/ --cz8u4a15S3Z8xhXIANZsSIz-PwimiGtKD0DIZFM Content-Type: text/html; charset=3DUTF-8 Content-Transfer-Encoding: 7bit =20  
=20 =20

Graham,

Thanks for all your hard work on updating and adding new features to op25.

--===============7426014581262678676==--