On Thu, Jun 28, 2018 at 6:21 PM ronnie sahlberg <ronniesahlberg@xxxxxxxxx> wrote: > > On Fri, Jun 29, 2018 at 8:58 AM, Theodore Y. Ts'o via samba-technical > <samba-technical@xxxxxxxxxxxxxxx> wrote: > > On Thu, Jun 28, 2018 at 05:37:15PM -0500, Steve French wrote: > >> Ronnie brought up an interesting point about the problems consistently > >> configuring file systems (or any Linux module for that matter) so that > >> reboot doesn't wipe away security or performance tuning changes. > > > > In general it's considered best practice to make the file system > > auto-tune itself as much as possible, because the sad fact is that > > 99.9999% of the customers aren't going to bother to add any tuning > > parameters. So there hasn't been a push to try to create something > > more complex, because it's generally not needed. > > True, but in these cases I think we are more looking at server or > mountpoint specific options than > actual fs tuning. > > For example nfsmount.conf can be used to say "only use NFSv4 when > accessing server abc" etc. > For the case of CIFS I could imagine that an administrator might want > to set "disable smb1 protocol globally" Or perhaps "disable smb1 on " ... various public networks but allow it on private networks -- Thanks, Steve -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
