Report #3664
baseband.trigger-prefix database value ignored by trigger subservice
sourcearmelthelae
version0.5.5
statusRES
priorityTRI
target fix0.5.7
report date2026-02-11 06:38:53
reportWhen attempting to set a custom trigger prefix via "@db set baseband.trigger-prefix " and restarting the trigger subservice via "@service baseband start trigger", the baseband.trigger-prefix database value is being ignored and the trigger subsystem is defaulting to the unit name instead of using the supplied value.
8 months ago rhet0rica: This is a general problem with baseband not reading configuration settings until it has been restarted completely (rendering its command interface redundant!); should be fixed for 0.5.7.
Please log in or register to add remarks.