Right now, the networking settings are only available via kernel module parameters. Maybe that's just fine, or maybe we want to (also or instead) have other means of configuration.
For other LKRG settings, we also support sysctl. For networking, this would take non-trivial effort to implement and maintain - e.g., would we reconnect to a new address if the server address is changed while LKRG is running and had already connected? Is this extra functionality desirable or a waste of resources to create and maintain?
Separately, we had found that LKRG configuration via sysctl and via module parameters is not ideal in different ways, so maybe we could want to introduce something else entirely - like a configuration file read by LKRG itself - for all of LKRG settings, including these.
Nov 10, 2022
Right now, the networking settings are only available via kernel module parameters. Maybe that's just fine, or maybe we want to (also or instead) have other means of configuration.
For other LKRG settings, we also support
sysctl. For networking, this would take non-trivial effort to implement and maintain - e.g., would we reconnect to a new address if the server address is changed while LKRG is running and had already connected? Is this extra functionality desirable or a waste of resources to create and maintain?Separately, we had found that LKRG configuration via
sysctland via module parameters is not ideal in different ways, so maybe we could want to introduce something else entirely - like a configuration file read by LKRG itself - for all of LKRG settings, including these.