This patch is a manpage update addressing the typos and mistakes in the vfs_smb_traffic_analyzer manpage and the smbta-util manpage, which have been brought up in these threads on samba-technical: http://lists.samba.org/archive/samba-technical/2011-May/077801.html http://lists.samba.org/archive/samba-technical/2011-May/077800.html http://lists.samba.org/archive/samba-technical/2011-May/077753.html
I have seen Volker already fixed the typos in
127d417e8ebc967572df7a75b342897a6a8fb71e , but I haven't found
"Ultimatively" in any dictionary, so this patch just removes the
word completely.
Thanks to Samba-JP oota <ribbon@samba.gr.jp> for reporting.
The last 2 patches address bug #8178 (Collection of manpage updates for SMB
Traffic Analyzer).
(cherry picked from commit
3e3b85f2796166109ce9a72f797a3ca708e7d186)
<cmdsynopsis>
<command>smbta-util</command>
<arg rep="repeat" choice="opt">
- <replaceable>COMMANDS</replaceable>
+ <replaceable>OPTIONS</replaceable>
</arg>
</cmdsynopsis>
<para>This tool is part of the
<citerefentry><refentrytitle>samba</refentrytitle>
- <manvolnum>1</manvolnum></citerefentry> suite.</para>
+ <manvolnum>7</manvolnum></citerefentry> suite.</para>
<para><command>smbta-util</command> is a tool to ease the
configuration of the vfs_smb_traffic_analyzer module regarding
<refsect1>
- <title>COMMANDS</title>
+ <title>OPTIONS</title>
<variablelist>
<refsect1>
<title>VERSION</title>
- <para>This man page is correct for version 3.4 of the Samba suite.</para>
+ <para>This man page is correct for version 3.6 of the Samba suite.</para>
</refsect1>
<refsect1>
The module now can identify itself against the receiver with a sub-release number, where
the receiver may run with a different sub-release number than the module. However, as
long as both run on the V2.x protocol, the receiver will not crash, even if the module
- uses features only implemented in the newer subrelease. Ultimatively, if the module uses
+ uses features only implemented in the newer subrelease. If the module uses
a new feature from a newer subrelease, and the receiver runs an older protocol, it is just
ignoring the functionality. Of course it is best to have both the receiver and the module
running the same subrelease of the protocol.