From 7617741e64ddc7db7e0fbf706289a14986a6139a Mon Sep 17 00:00:00 2001 From: Christoph Zauner Date: Wed, 11 Jun 2008 15:17:21 +0200 Subject: man pages: Fix typos. (This used to be commit 881eaa26e071a7fde9c6fc5eb42ae122d0ddd490) --- docs-xml/smbdotconf/base/bindinterfacesonly.xml | 6 +++--- docs-xml/smbdotconf/ldap/ldapsameditposix.xml | 3 +-- docs-xml/smbdotconf/printing/addprintercommand.xml | 10 ++++++---- docs-xml/smbdotconf/printing/deleteprintercommand.xml | 6 +++--- docs-xml/smbdotconf/security/ntlmauth.xml | 2 +- docs-xml/smbdotconf/security/passwdchat.xml | 2 +- 6 files changed, 15 insertions(+), 14 deletions(-) diff --git a/docs-xml/smbdotconf/base/bindinterfacesonly.xml b/docs-xml/smbdotconf/base/bindinterfacesonly.xml index bccac4a0da..6e8321bbca 100644 --- a/docs-xml/smbdotconf/base/bindinterfacesonly.xml +++ b/docs-xml/smbdotconf/base/bindinterfacesonly.xml @@ -29,14 +29,14 @@ For file service it causes smbd 8 to bind only to the interface list given in the parameter. This restricts the networks that smbd will - serve to packets coming in those interfaces. Note that you should not use this parameter for machines that + serve, to packets coming in on those interfaces. Note that you should not use this parameter for machines that are serving PPP or other intermittent or non-broadcast network interfaces as it will not cope with non-permanent interfaces. - If is set then unless the network address - 127.0.0.1 is added to the parameter list + If is set and the network address + 127.0.0.1 is not added to the parameter list smbpasswd 8 and swat 8 may not work as expected due to the reasons covered below. diff --git a/docs-xml/smbdotconf/ldap/ldapsameditposix.xml b/docs-xml/smbdotconf/ldap/ldapsameditposix.xml index ace6c6c64d..c04ecc9cdd 100644 --- a/docs-xml/smbdotconf/ldap/ldapsameditposix.xml +++ b/docs-xml/smbdotconf/ldap/ldapsameditposix.xml @@ -48,8 +48,7 @@ idmap gid = 5000-50000 - This configuration assume the ldap server have been loaded with a base tree like described - in the following ldif: + This configuration assumes a directory layout like described in the following ldif: dn: dc=samba,dc=org diff --git a/docs-xml/smbdotconf/printing/addprintercommand.xml b/docs-xml/smbdotconf/printing/addprintercommand.xml index ed3c5aa3be..c66f43eb3f 100644 --- a/docs-xml/smbdotconf/printing/addprintercommand.xml +++ b/docs-xml/smbdotconf/printing/addprintercommand.xml @@ -1,4 +1,4 @@ - For a Samba host this means that the printer must be - physically added to the underlying printing system. The add - printer command defines a script to be run which + physically added to the underlying printing system. + The addprinter command + defines a script to be run which will perform the necessary operations for adding the printer to the print system and to add the appropriate service definition to the smb.conf file in order that it can be @@ -46,7 +47,8 @@ will return an ACCESS_DENIED error to the client. - The "add printer command" program can output a single line of text, + The addprinter command program + can output a single line of text, which Samba will set as the port the new printer is connected to. If this line isn't output, Samba won't reload its printer shares. diff --git a/docs-xml/smbdotconf/printing/deleteprintercommand.xml b/docs-xml/smbdotconf/printing/deleteprintercommand.xml index b48ab5700d..d9a3fddfb9 100644 --- a/docs-xml/smbdotconf/printing/deleteprintercommand.xml +++ b/docs-xml/smbdotconf/printing/deleteprintercommand.xml @@ -6,11 +6,11 @@ With the introduction of MS-RPC based printer support for Windows NT/2000 clients in Samba 2.2, it is now - possible to delete printer at run time by issuing the + possible to a delete printer at run time by issuing the DeletePrinter() RPC call. For a Samba host this means that the printer must be - physically deleted from underlying printing system. The + physically deleted from the underlying printing system. The defines a script to be run which will perform the necessary operations for removing the printer from the print system and from smb.conf. @@ -22,7 +22,7 @@ Once the has been executed, smbd will reparse the - smb.conf to associated printer no longer exists. + smb.conf to check that the associated printer no longer exists. If the sharename is still valid, then smbd will return an ACCESS_DENIED error to the client. diff --git a/docs-xml/smbdotconf/security/ntlmauth.xml b/docs-xml/smbdotconf/security/ntlmauth.xml index ebcdad72a1..ec603bbf59 100644 --- a/docs-xml/smbdotconf/security/ntlmauth.xml +++ b/docs-xml/smbdotconf/security/ntlmauth.xml @@ -13,7 +13,7 @@ If this option, and lanman auth are both disabled, then only NTLMv2 logins will be permited. Not all clients support NTLMv2, and most will require - special configuration to us it. + special configuration to use it. yes diff --git a/docs-xml/smbdotconf/security/passwdchat.xml b/docs-xml/smbdotconf/security/passwdchat.xml index da18142dfa..13db519f40 100644 --- a/docs-xml/smbdotconf/security/passwdchat.xml +++ b/docs-xml/smbdotconf/security/passwdchat.xml @@ -17,7 +17,7 @@ on what local methods are used for password control (such as NIS etc). - Note that this parameter only is only used if the Note that this parameter only is used if the parameter is set to yes. This sequence is then called AS ROOT when the SMB password in the smbpasswd file is being changed, without access to the old password -- cgit