Report #3665
Setting trigger prefix does not take. (Re)starting the trigger service always defaults to unit name.
| source | Nensec |
|---|---|
| version | 0.5.5 |
| status | DUP |
| priority | TRI |
| target fix | 0.5.7 |
| report date | 2026-02-27 13:15:11 |
| report | Attempted to set the trigger prefix via the command, according to the wiki: @db set baseband.trigger-prefix Voi-Voi Then restarted the trigger service @service baseband stop trigger @service baseband start trigger Resulted in: [17:31:17] :: modified baseband setting trigger-prefix: (undefined) --> Voi-Voi [17:31:40] APS V01: [_baseband] stopping network service trigger [17:31:46] APS V01: [_baseband] no trigger prefix set; defaulting to V01 [17:31:46] APS V01: [_baseband] started network service trigger This did not work, tried without the hyphen in case that was the cause: [17:45:41] :: modified baseband setting trigger-prefix: Voi-Voi --> VoiVoi [17:45:54] APS V01: [_baseband] stopping network service trigger [17:45:59] APS V01: [_baseband] no trigger prefix set; defaulting to V01 [17:45:59] APS V01: [_baseband] started network service trigger |
7 months ago
rhet0rica:
Dupe of 3664. Fixed in 0.5.7.