I think this is a reasonable idea - and nfs-utils's parsing for this config file (in mount.nfs e.g.) may be similar enough to smb3 requirements in some cases - but don't rule out the idea of seeing if anything is shareable/reuseable with Samba (to allow e.g. smbcacls or small client utilities to benefit from cifs.ko configuration and vice versa). In addition don't rule out the idea of writing small cifs-utils that allow sane setting of the text configuration file (ala "net conf <section> <keyword> <value>" or equivalent. One of the curses of many text config files is difficulty figuring out options/syntax etc. and making spelling mistakes so in a perfect world the user could set the config file values with an easy to use cifs-util tool (vaguely similar to "net conf ..." perhaps) If we allow setting the 5-10 module install parms and then the things configurable in /proc/fs/cifs/* ... we would need some way to load them on reboot. The nfs example may be useful but it is more focused on mount parms it seems rather than other config values. But if you want to pursue this it seems promising to investigate nfsmount.conf and whether there is something vaguely similar we could do for smb3 but ... I would prefer if along with that we had an easy to use tool to set the values and provide help on the valid options etc. (there may be a lot we can also learn by the way from other fs tools as models - e.g. "iostat" and "nfsiostat" if looking at these tools for other file systems) On Thu, Jun 28, 2018 at 9:35 PM Kenneth Dsouza <kdsouza@xxxxxxxxxx> wrote: > > > I was just wondering why we don't have a /etc/cifsmount.conf just like /etc/nfsmount.conf for mount options. I would like to work on it, if we can add this functionality. > Using this we can easily disable smb1. > > Regards, > Kenneth D'souza -- 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
