svxlink
svxlink copied to clipboard
sm0svx
REQ: svxreflector implementaion for SIGHUP (re-read config without restart)
I wish svxreflector daemon implemented the SIGHUP signal in order to re-read the config file without having to kill the process and restart it.
This would be useful to enforce config changes (like new users or user deletions) without affecting the present connections.
Open to other suggestions to achieve the same goal.
It find it takes only seconds for the implementation of a restart, that barely makes a flicker on the portal dashboard. I see no real issues, it's not a professional communications system however you look at it, as good as it is. Chris
On Fri, 15 Mar 2024, 18:56 Audric IW1GEU, @.***> wrote:
I wish svxreflector daemon implemented the SIGHUP signal in order to re-read the config file without having to kill the process and restarting it.
This would be useful to enforce config changes (like new users or user deletions) without affecting the present connections.
Open to other suggestions that achieve the same goal.
— Reply to this email directly, view it on GitHub https://github.com/sm0svx/svxlink/issues/665, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACAKA5F64SKUL2BBN3XUE2DYYM77PAVCNFSM6AAAAABEYQE5BWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGE4DSMRYGIYTQMI . You are receiving this because you are subscribed to this thread.Message ID: @.***>
As @f5vmr commented, a reflector restart is normally hardly noticeable even when in the middle of a QSO. As for user additions/deletions, you should not use the AUTH_KEY authentication anymore but certificates.
A complete re-read of the config would be a lot of work to implement so it will not happen. A couple of variables are settable at run-time using the COMMAND_PTY (GLOBAL/SQL_TIMEOUT_BLOCKTIME and GLOBAL/SQL_TIMEOUT). And if you really want to, you can also add entries to the USERS and PASSWORDS section at run-time. They will not be stored in the config file though so you will have to do that manually.
Because the 2 UK reflectors are built on version 24, TYPE=ReflectorV2 is required on Version 25 units. One day we might get round to changing it, but with many users on Version 24, it's a project.
When I add new users with an AUTH_KEY, and perform a restart by systemctl there is negligible stoppage.
Chris
On Sun, 28 Sept 2025, 12:50 Tobias Blomberg, @.***> wrote:
sm0svx left a comment (sm0svx/svxlink#665) https://github.com/sm0svx/svxlink/issues/665#issuecomment-3343043458
As @f5vmr https://github.com/f5vmr commented, a reflector restart is normally hardly noticeable even when in the middle of a QSO. As for user additions/deletions, you should not use the AUTH_KEY authentication anymore but certificates.
A complete re-read of the config would be a lot of work to implement so it will not happen. A couple of variables are settable at run-time using the COMMAND_PTY (GLOBAL/SQL_TIMEOUT_BLOCKTIME and GLOBAL/SQL_TIMEOUT). And if you really want to, you can also add entries to the USERS and PASSWORDS section at run-time. They will not be stored in the config file though so you will have to do that manually.
— Reply to this email directly, view it on GitHub https://github.com/sm0svx/svxlink/issues/665#issuecomment-3343043458, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACAKA5CK47XHJX7ECMQZHCD3U7DQFAVCNFSM6AAAAACHWVEINKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGNBTGA2DGNBVHA . You are receiving this because you were mentioned.Message ID: @.***>
On the reflector side it's not a problem. The latest reflector software will support older clients just fine so start by upgrading those old reflectors. Nothing will change really until some node connect using the V3 protocol.
On the Swedish reflector the oldest V2 node is running SvxLink 1.7.99.52 and all reflectors are obviously running the latest development code from git master.
Ok, I'll check it out. Thanks Chris
On Sun, 28 Sept 2025, 13:48 Tobias Blomberg, @.***> wrote:
sm0svx left a comment (sm0svx/svxlink#665) https://github.com/sm0svx/svxlink/issues/665#issuecomment-3343205176
On the Swedish reflector the oldest V2 node is running SvxLink 1.7.99.52 and all reflectors are obviously running the latest development code from git master.
— Reply to this email directly, view it on GitHub https://github.com/sm0svx/svxlink/issues/665#issuecomment-3343205176, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACAKA5GTYM6WYLGUWUHTFI33U7KINAVCNFSM6AAAAACHWVEINKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGNBTGIYDKMJXGY . You are receiving this because you were mentioned.Message ID: @.***>