On Fri, Feb 21, 2014 at 12:48:56PM +0100, Richard Cochran wrote: > > Do we need to do that? The default value (set in ptp4l.c) means this option > > is disabled and I do not think many people will want to use it. I would > > argue > > that it adds noise to the default configuration files, but if the > > policy is that every option has to be present in default configuration files > > I will add it. Opinions? > > If this option is somehow useful for gPTP applications, then I think > it should at least appear in gPTP.cfg.
I thought default.cfg listed all options and their default values so one doesn't have to look in the man page. There are other options that probably won't be set very often, and even clock_servo which has only one allowed value. > Also, on second thought, maybe INT_MIN is too extreme as a default > value. Since the default neighborPropDelayThresh is 20ms, maybe using > something like -20ms is more balanced. I mean, the propagation delay > cannot possibly get so far out, can it? Yeah, INT_MIN wouldn't look very nice in the config :). -- Miroslav Lichvar ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
