| Message ID | 49E46916.2040103@suse.de (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
Hi Steve, Jeff, If the following mount.cifs doc patch makes sense, can this be considered for merging? I have seen atleast a couple of bug reports that reports that cifs is not honoring configuration setting in smb.conf. Thanks, Suresh Jayaraman wrote: > It seems that for some users that are used to smbclient, it is not clear > that mount.cifs never uses smb.conf for configuring client specific > parameters. So, let's add this information to mount.cifs man page. > > Signed-off-by: Suresh Jayaraman <sjayaraman@suse.de> > --- > > docs-xml/manpages-3/mount.cifs.8.xml | 6 ++++++ > 1 files changed, 6 insertions(+), 0 deletions(-) > > diff --git a/docs-xml/manpages-3/mount.cifs.8.xml b/docs-xml/manpages-3/mount.cifs.8.xml > index d0affea..32b2970 100644 > --- a/docs-xml/manpages-3/mount.cifs.8.xml > +++ b/docs-xml/manpages-3/mount.cifs.8.xml > @@ -65,6 +65,12 @@ kernel log. > the mounted resource is unmounted (usually via the umount utility). > </para> > > + <para> > + Some samba client tools like smbclient(8) honours client-side > + configuration parameters present in smb.conf. Unlike those client tools, > + <emphasis>mount.cifs</emphasis> ignores smb.conf completely. > + </para> > + > </refsect1> > > <refsect1> > _______________________________________________ > linux-cifs-client mailing list > linux-cifs-client@lists.samba.org > https://lists.samba.org/mailman/listinfo/linux-cifs-client
On Mon, 20 Apr 2009 10:09:12 +0530 Suresh Jayaraman <sjayaraman@suse.de> wrote: > Hi Steve, Jeff, > > If the following mount.cifs doc patch makes sense, can this be > considered for merging? I have seen atleast a couple of bug reports that > reports that cifs is not honoring configuration setting in smb.conf. > > Thanks, > > Suresh Jayaraman wrote: > > It seems that for some users that are used to smbclient, it is not clear > > that mount.cifs never uses smb.conf for configuring client specific > > parameters. So, let's add this information to mount.cifs man page. > > > > Signed-off-by: Suresh Jayaraman <sjayaraman@suse.de> > > --- > > > > docs-xml/manpages-3/mount.cifs.8.xml | 6 ++++++ > > 1 files changed, 6 insertions(+), 0 deletions(-) > > > > diff --git a/docs-xml/manpages-3/mount.cifs.8.xml b/docs-xml/manpages-3/mount.cifs.8.xml > > index d0affea..32b2970 100644 > > --- a/docs-xml/manpages-3/mount.cifs.8.xml > > +++ b/docs-xml/manpages-3/mount.cifs.8.xml > > @@ -65,6 +65,12 @@ kernel log. > > the mounted resource is unmounted (usually via the umount utility). > > </para> > > > > + <para> > > + Some samba client tools like smbclient(8) honours client-side ^^^^^^^ Should be "honour" > > + configuration parameters present in smb.conf. Unlike those client tools, > > + <emphasis>mount.cifs</emphasis> ignores smb.conf completely. > > + </para> > > + > > </refsect1> > > > > <refsect1> Maybe this should go in the NOTES section?
diff --git a/docs-xml/manpages-3/mount.cifs.8.xml b/docs-xml/manpages-3/mount.cifs.8.xml index d0affea..32b2970 100644 --- a/docs-xml/manpages-3/mount.cifs.8.xml +++ b/docs-xml/manpages-3/mount.cifs.8.xml @@ -65,6 +65,12 @@ kernel log. the mounted resource is unmounted (usually via the umount utility). </para> + <para> + Some samba client tools like smbclient(8) honours client-side + configuration parameters present in smb.conf. Unlike those client tools, + <emphasis>mount.cifs</emphasis> ignores smb.conf completely. + </para> + </refsect1> <refsect1>
It seems that for some users that are used to smbclient, it is not clear that mount.cifs never uses smb.conf for configuring client specific parameters. So, let's add this information to mount.cifs man page. Signed-off-by: Suresh Jayaraman <sjayaraman@suse.de> --- docs-xml/manpages-3/mount.cifs.8.xml | 6 ++++++ 1 files changed, 6 insertions(+), 0 deletions(-)