e...@thyrsus.com said:
>> Do you have an example of where we need to change a
>> driver variable on the fly?
> No, I'm bothered because I'm (a) not sure we'll never need to do it, and (b)
> pretty sure what the Dread God Finagle will arrange if I assume we won't. :-)
I just looked at the code. There is a table for refclocks. All are RO.
While I was there, I searched some more. There is only one RW in the whole
file:
* System variable values. The array can be indexed by the variable
* index to find the textual name. Mostly not order-sensitive.
*/
static const struct ctl_var sys_var[] = {
{ 0, PADDING, "" },
#define CS_LEAP 1
{ CS_LEAP, RW|DEF, "leap" },
I'd be willing to change that to RO and drop the whole idea of writing things
via ntpq.
That would leave the configure option. I've never used it.
--
These are my opinions. I hate spam.
_______________________________________________
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
