On Mar 18, 2008, at 4:47 AM, James Carlson wrote: > Nicolas Williams writes: >> On Mon, Mar 17, 2008 at 06:55:54PM -0400, Jeffrey Hutzelman wrote: >>> I'm inclined to prefer that parameters set in the config file >>> (especially >>> one given explicitly on the command line) take precedence over >>> those found >>> in SMF. In fact, I believe this is necessary in order to satisfy >>> the >>> principle of least surprise. Similarly, the as-shipped >>> sshd_config should >>> contain a comment to the effect that parameters may be set in SMF. >> >> I was inclined to think the opposite... (so that a single config file >> could be shared by multiple instances with overrides in SMF for >> parameters that differ). > > I can see the command line parameters overriding SMF, but I'm not sure > I agree with having the text config file preferred over SMF.
I'm not taking a position one way or the other, but I note that this list is a biased sample to answer this question. Many of Sun's customers have a lot invested in non-Sun configurations as well. Whether they would prefer to have their non-Sun ssh[d]_config files work as-is (least surprise?), or to have a SMF be a place to put just a few Sun-unique overrides I can't say. ------------------------------------------------------------------------ The opinions expressed in this message are mine, not those of Caltech, JPL, NASA, or the US Government. Henry.B.Hotz at jpl.nasa.gov, or hbhotz at oxy.edu
