From 0685f504b85a788ecf2d4975c512d5c529bd5b1a Mon Sep 17 00:00:00 2001 From: Benjamin Brunner Date: Fri, 27 May 2011 12:39:41 +0200 Subject: [PATCH] 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 for reporting. --- docs-xml/manpages-3/smbta-util.8.xml | 8 ++++---- docs-xml/manpages-3/vfs_smb_traffic_analyzer.8.xml | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs-xml/manpages-3/smbta-util.8.xml b/docs-xml/manpages-3/smbta-util.8.xml index 6e53aaa..3a88f7b 100644 --- a/docs-xml/manpages-3/smbta-util.8.xml +++ b/docs-xml/manpages-3/smbta-util.8.xml @@ -25,7 +25,7 @@ smbta-util - COMMANDS + OPTIONS @@ -36,7 +36,7 @@ This tool is part of the samba - 1 suite. + 7 suite. smbta-util is a tool to ease the configuration of the vfs_smb_traffic_analyzer module regarding @@ -52,7 +52,7 @@ - COMMANDS + OPTIONS @@ -103,7 +103,7 @@ VERSION - This man page is correct for version 3.4 of the Samba suite. + This man page is correct for version 3.6 of the Samba suite. diff --git a/docs-xml/manpages-3/vfs_smb_traffic_analyzer.8.xml b/docs-xml/manpages-3/vfs_smb_traffic_analyzer.8.xml index 8df9751..44c37ce 100644 --- a/docs-xml/manpages-3/vfs_smb_traffic_analyzer.8.xml +++ b/docs-xml/manpages-3/vfs_smb_traffic_analyzer.8.xml @@ -139,7 +139,7 @@ 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. -- 1.7.3.4