From: Andreas Schneider Date: Thu, 14 Jul 2022 08:05:53 +0000 (+0200) Subject: docs-xml: Remove trailing whitespaces in rpcclient.1.xml X-Git-Tag: samba-4.17.0rc1~198 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=c557259dd9589e10ed9ed613532ba3d88cf2f795;p=thirdparty%2Fsamba.git docs-xml: Remove trailing whitespaces in rpcclient.1.xml Signed-off-by: Andreas Schneider Reviewed-by: Stefan Metzmacher --- diff --git a/docs-xml/manpages/rpcclient.1.xml b/docs-xml/manpages/rpcclient.1.xml index 7c0c380cd8d..cc654e35803 100644 --- a/docs-xml/manpages/rpcclient.1.xml +++ b/docs-xml/manpages/rpcclient.1.xml @@ -13,7 +13,7 @@ rpcclient - tool for executing client side + tool for executing client side MS-RPC functions @@ -62,9 +62,9 @@ 7 suite. rpcclient is a utility initially developed - to test MS-RPC functionality in Samba itself. It has undergone + to test MS-RPC functionality in Samba itself. It has undergone several stages of development and stability. Many system administrators - have now written scripts around it to manage Windows NT clients from + have now written scripts around it to manage Windows NT clients from their UNIX workstation. @@ -148,22 +148,22 @@ below) - + -I|--dest-ip IP-address - IP address is the address of the server to connect to. + IP address is the address of the server to connect to. It should be specified in standard "a.b.c.d" notation. - Normally the client would attempt to locate a named - SMB/CIFS server by looking it up via the NetBIOS name resolution - mechanism described above in the name resolve order + Normally the client would attempt to locate a named + SMB/CIFS server by looking it up via the NetBIOS name resolution + mechanism described above in the name resolve order parameter above. Using this parameter will force the client - to assume that the server is on the machine with the specified IP - address and the NetBIOS name component of the resource being + to assume that the server is on the machine with the specified IP + address and the NetBIOS name component of the resource being connected to will be ignored. - There is no default for this parameter. If not supplied, - it will be determined automatically by the client as described + There is no default for this parameter. If not supplied, + it will be determined automatically by the client as described above. @@ -323,17 +323,17 @@ SPOOLSS - adddriver <arch> <config> [<version>] + adddriver <arch> <config> [<version>] - Execute an AddPrinterDriver() RPC to install the printer driver - information on the server. Note that the driver files should - already exist in the directory returned by - getdriverdir. Possible values for - arch are the same as those for + Execute an AddPrinterDriver() RPC to install the printer driver + information on the server. Note that the driver files should + already exist in the directory returned by + getdriverdir. Possible values for + arch are the same as those for the getdriverdir command. - The config parameter is defined as + The config parameter is defined as follows: - + Long Driver Name:\ Driver File Name:\ @@ -346,12 +346,12 @@ Comma Separated list of Files Any empty fields should be enter as the string "NULL". - + Samba does not need to support the concept of Print Monitors since these only apply to local printers whose driver can make - use of a bi-directional link for communication. This field should - be "NULL". On a remote NT print server, the Print Monitor for a - driver must already be installed prior to adding the driver or + use of a bi-directional link for communication. This field should + be "NULL". On a remote NT print server, the Print Monitor for a + driver must already be installed prior to adding the driver or else the RPC will fail. The version parameter lets you @@ -360,12 +360,12 @@ Comma Separated list of Files be used. This option can be used to upload Windows 2000 (version 3) printer drivers. - addprinter <printername> + addprinter <printername> <sharename> <drivername> <port> - Add a printer on the remote server. This printer - will be automatically shared. Be aware that the printer driver - must already be installed on the server (see adddriver) + Add a printer on the remote server. This printer + will be automatically shared. Be aware that the printer driver + must already be installed on the server (see adddriver) and the portmust be a valid port name (see enumports. @@ -385,9 +385,9 @@ Comma Separated list of Files of 3 requests (DPD_DELETE_UNUSED_FILES | DPD_DELETE_SPECIFIC_VERSION). - enumdataEnumerate all - printer setting data stored on the server. On Windows NT clients, - these values are stored in the registry, while Samba servers + enumdataEnumerate all + printer setting data stored on the server. On Windows NT clients, + these values are stored in the registry, while Samba servers store them in the printers TDB. This command corresponds to the MS Platform SDK GetPrinterData() function (* This command is currently unimplemented). @@ -397,8 +397,8 @@ Comma Separated list of Files enumkeyEnumerate printer keys enumjobs <printer> - List the jobs and status of a given printer. - This command corresponds to the MS Platform SDK EnumJobs() + List the jobs and status of a given printer. + This command corresponds to the MS Platform SDK EnumJobs() function getjobGet print job @@ -407,38 +407,38 @@ Comma Separated list of Files enumports [level] - Executes an EnumPorts() call using the specified - info level. Currently only info levels 1 and 2 are supported. + Executes an EnumPorts() call using the specified + info level. Currently only info levels 1 and 2 are supported. - enumdrivers [level] + enumdrivers [level] - Execute an EnumPrinterDrivers() call. This lists the various installed - printer drivers for all architectures. Refer to the MS Platform SDK - documentation for more details of the various flags and calling + Execute an EnumPrinterDrivers() call. This lists the various installed + printer drivers for all architectures. Refer to the MS Platform SDK + documentation for more details of the various flags and calling options. Currently supported info levels are 1, 2, and 3. enumprinters [level] - Execute an EnumPrinters() call. This lists the various installed - and share printers. Refer to the MS Platform SDK documentation for + Execute an EnumPrinters() call. This lists the various installed + and share printers. Refer to the MS Platform SDK documentation for more details of the various flags and calling options. Currently supported info levels are 1, 2 and 5. - getdata <printername> <valuename;> - Retrieve the data for a given printer setting. See - the enumdata command for more information. - This command corresponds to the GetPrinterData() MS Platform + getdata <printername> <valuename;> + Retrieve the data for a given printer setting. See + the enumdata command for more information. + This command corresponds to the GetPrinterData() MS Platform SDK function. getdataexGet printer driver data with keyname - + getdriver <printername> - Retrieve the printer driver information (such as driver file, - config file, dependent files, etc...) for + Retrieve the printer driver information (such as driver file, + config file, dependent files, etc...) for the given printer. This command corresponds to the GetPrinterDriver() MS Platform SDK function. Currently info level 1, 2, and 3 are supported. @@ -446,23 +446,23 @@ Comma Separated list of Files getdriverdir <arch> Execute a GetPrinterDriverDirectory() - RPC to retrieve the SMB share name and subdirectory for - storing printer driver files for a given architecture. Possible - values for arch are "Windows 4.0" + RPC to retrieve the SMB share name and subdirectory for + storing printer driver files for a given architecture. Possible + values for arch are "Windows 4.0" (for Windows 95/98), "Windows NT x86", "Windows NT PowerPC", "Windows Alpha_AXP", and "Windows NT R4000". getdriverpackagepath Get print driver package download directory - getprinter <printername> - Retrieve the current printer information. This command - corresponds to the GetPrinter() MS Platform SDK function. + getprinter <printername> + Retrieve the current printer information. This command + corresponds to the GetPrinter() MS Platform SDK function. - openprinter <printername> - Execute an OpenPrinterEx() and ClosePrinter() RPC + openprinter <printername> + Execute an OpenPrinterEx() and ClosePrinter() RPC against a given printer. openprinter_ex <printername> @@ -474,7 +474,7 @@ Comma Separated list of Files associated with an installed printer. The printer driver must already be correctly installed on the print server. - See also the enumprinters and + See also the enumprinters and enumdrivers commands for obtaining a list of of installed printers and drivers. @@ -705,28 +705,28 @@ Comma Separated list of Files BUGS - - rpcclient is designed as a developer testing tool - and may not be robust in certain areas (such as command line parsing). - It has been known to generate a core dump upon failures when invalid + + rpcclient is designed as a developer testing tool + and may not be robust in certain areas (such as command line parsing). + It has been known to generate a core dump upon failures when invalid parameters where passed to the interpreter. From Luke Leighton's original rpcclient man page: - - WARNING! The MSRPC over SMB code has - been developed from examining Network traces. No documentation is - available from the original creators (Microsoft) on how MSRPC over - SMB works, or how the individual MSRPC services work. Microsoft's - implementation of these services has been demonstrated (and reported) + + WARNING! The MSRPC over SMB code has + been developed from examining Network traces. No documentation is + available from the original creators (Microsoft) on how MSRPC over + SMB works, or how the individual MSRPC services work. Microsoft's + implementation of these services has been demonstrated (and reported) to be... a bit flaky in places. - The development of Samba's implementation is also a bit rough, - and as more of the services are understood, it can even result in + The development of Samba's implementation is also a bit rough, + and as more of the services are understood, it can even result in versions of smbd 8 and rpcclient - 1 that are incompatible for some commands or services. Additionally, - the developers are sending reports to Microsoft, and problems found - or reported to Microsoft are fixed in Service Packs, which may + 1 that are incompatible for some commands or services. Additionally, + the developers are sending reports to Microsoft, and problems found + or reported to Microsoft are fixed in Service Packs, which may result in incompatibilities. @@ -740,15 +740,15 @@ Comma Separated list of Files AUTHOR - - The original Samba software and related utilities + + The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed - by the Samba Team as an Open Source project similar + by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. - - The original rpcclient man page was written by Matthew - Geddes, Luke Kenneth Casson Leighton, and rewritten by Gerald Carter. - The conversion to DocBook for Samba 2.2 was done by Gerald + + The original rpcclient man page was written by Matthew + Geddes, Luke Kenneth Casson Leighton, and rewritten by Gerald Carter. + The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.