Open SchoolGuy opened 7 months ago
The reason for using the -stats.sh
approach is to make it easier for the user to configure the specified bind, and also to customize some other additional actions on that script.
If you have other good ideas, you can discuss them together!
The script requires the following information:
The golang binary currently has already information in a configurable manner about the first thing. In my eyes it is acceptable to introduce a new option called bind.binary
with a default of /usr/sbin/rndc
.
Here we could then directly call the command and add an unlink command to the stats file beforehand:
The script requires the following information:
- location of the stats file (currently hardcoded in the script)
- location of rndc (currently hardcoded in the script)
The golang binary currently has already information in a configurable manner about the first thing. In my eyes it is acceptable to introduce a new option called
bind.binary
with a default of/usr/sbin/rndc
.Here we could then directly call the command and add an unlink command to the stats file beforehand:
I think it's possible, you can realize it. It's going to be very rewarding!
This package comes with a script called
stats.sh
. I would love to understand why this approach was chosen instead of calling the corresponding commands directly from golang.If there is no particular reason I would love to try and contribute code to replace it (it might take a good long while though due to my load atm).