Hal, You raise a frustrating issue. It would be easy to add all kinds of things to the server line; however, the mobilization routine has a fixed format consistent with the ntpdc association managment code. Presumably, the new ntpq can do many things using existing configuration file commands, so changing the format might not matter. However, attempts to withdraw ntpdc have met with nasty howls of pain for one reason or another.
Perhaps the best way is to add a completely new command "refclock" and load it up with all kinds of options, including those now done by the fudge command. The command would not need the dotted quad, which could be replaced by the driver name already in a table. The syntax could in principle be different for each name, as determined by the parser. That could be a nice summer project. Dave Hal Murray wrote: >>The NMEA driver uses 3 mode bits. I think more are available. >>The docs say that flag1 is unused for the NMEA driver. > > > It would be really nice if there was a clean way to specify the > baud rate. > > Several of the NMEA units I'm familiar with allow you to set > the baud rate they use. I expect there are times when it would > be nice to run faster than 4800. > > > >>You could also see if the initial stock probes return valid data, and if not >>switch to the baud rate you need for your clock and try it that way instead >>(which would obviate the need for any flag bits). > > > Do you want to maintain that sort of code? Let's not go there. > > > >>And now that we are rolling out the new config parser there is the >>possibility for a new config file format that will include the baud rate. > > > That would be great. Are there any examples of adding an option to > the server line? > _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
