From 69735a73b0baf021a2f395ae3c7915655201ef6f Mon Sep 17 00:00:00 2001 From: Andrew Bartlett Date: Tue, 21 May 2013 17:49:55 +1000 Subject: [PATCH 1/4] docs: Remove out of date and unmaintained Speed page from the HOWTO Reviewed-by: Jeremy Allison (cherry picked from commit fa8e760882ea389f8c94d6dfdc7386b0295974d1) --- docs-xml/Samba3-HOWTO/TOSHARG-Speed.xml | 327 -------------------------------- docs-xml/Samba3-HOWTO/index.xml | 2 - 2 files changed, 329 deletions(-) delete mode 100644 docs-xml/Samba3-HOWTO/TOSHARG-Speed.xml diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-Speed.xml b/docs-xml/Samba3-HOWTO/TOSHARG-Speed.xml deleted file mode 100644 index 18a15ae..0000000 --- a/docs-xml/Samba3-HOWTO/TOSHARG-Speed.xml +++ /dev/null @@ -1,327 +0,0 @@ - - - - - - - PaulCochrane - - Dundee Limb Fitting Centre -
paulc@dth.scot.nhs.uk
- - - &author.jelmer; - &author.jht; - - -Samba Performance Tuning - - -Comparisons - - -The Samba server uses TCP to talk to the client, so if you are -trying to see if it performs well, you should really compare it to -programs that use the same protocol. The most readily available -programs for file transfer that use TCP are ftp or another TCP-based -SMB server. - - - -If you want to test against something like an NT or Windows for Workgroups server, then -you will have to disable all but TCP on either the client or -server. Otherwise, you may well be using a totally different protocol -(such as NetBEUI) and comparisons may not be valid. - - - -Generally, you should find that Samba performs similarly to ftp at raw -transfer speed. It should perform quite a bit faster than NFS, -although this depends on your system. - - - -Several people have done comparisons between Samba and Novell, NFS, or -Windows NT. In some cases Samba performed the best, in others the worst. I -suspect the biggest factor is not Samba versus some other system, but the -hardware and drivers used on the various systems. Given similar -hardware, Samba should certainly be competitive in speed with other -systems. - - - - - -Socket Options - - -There are a number of socket options that can greatly affect the -performance of a TCP-based server like Samba. - - - -The socket options that Samba uses are settable both on the command -line with the option and in the &smb.conf; file. - - - -The section of the &smb.conf; manual page describes how -to set these and gives recommendations. - - - -Getting the socket options correct can make a big difference to your -performance, but getting them wrong can degrade it by just as -much. The correct settings are very dependent on your local network. - - - -The socket option TCP_NODELAY is the one that seems to make the biggest single difference -for most networks. Many people report that adding -TCP_NODELAY -doubles the read performance of a Samba drive. The best explanation I have seen for -this is that the Microsoft TCP/IP stack is slow in sending TCP ACKs. - - - -There have been reports that setting socket options = SO_RCVBUF=8192 in smb.conf -can seriously degrade Samba performance on the loopback adaptor (IP Address 127.0.0.1). It is strongly -recommended that before specifying any settings for socket options, the effect -first be quantitatively measured on the server being configured. - - - - - -Read Size - - -The option affects the overlap of disk -reads/writes with network reads/writes. If the amount of data being -transferred in several of the SMB commands (currently SMBwrite, SMBwriteX, and -SMBreadbraw) is larger than this value, then the server begins writing -the data before it has received the whole packet from the network, or -in the case of SMBreadbraw, it begins writing to the network before -all the data has been read from disk. - - - -This overlapping works best when the speeds of disk and network access -are similar, having little effect when the speed of one is much -greater than the other. - - - -The default value is 16384, but little experimentation has been -done as yet to determine the optimal value, and it is likely that the best -value will vary greatly between systems anyway. A value over 65536 is -pointless and will cause you to allocate memory unnecessarily. - - - - - -Max Xmit - - - At startup the client and server negotiate a maximum transmit size, -which limits the size of nearly all SMB commands. You can set the -maximum size that Samba will negotiate using the option -in &smb.conf;. Note that this is the maximum size of SMB requests that -Samba will accept, but not the maximum size that the client will accept. -The client maximum receive size is sent to Samba by the client, and Samba -honors this limit. - - - -It defaults to 65536 bytes (the maximum), but it is possible that some -clients may perform better with a smaller transmit unit. Trying values -of less than 2048 is likely to cause severe problems. -In most cases the default is the best option. - - - - - -Log Level - - -If you set the log level (also known as ) higher than 2, -then you may suffer a large drop in performance. This is because the -server flushes the log file after each operation, which can be quite -expensive. - - - - -Read Raw - - -The operation is designed to be an optimized, low-latency -file read operation. A server may choose to not support it, -however, and Samba makes support for optional, with it -being enabled by default. - - - -In some cases clients do not handle very well and actually -get lower performance using it than they get using the conventional -read operations, so you might like to try no and see what happens on your -network. It might lower, raise, or not affect your performance. Only -testing can really tell. - - - - - -Write Raw - - -The operation is designed to be an optimized, low-latency -file write operation. A server may choose to not support it, however, and Samba makes support for - optional, with it being enabled by default. - - - -Some machines may find slower than normal write, in which -case you may wish to change this option. - - - - - -Slow Logins - - -Slow logins are almost always due to the password checking time. Using -the lowest practical will improve things. - - - - - -Client Tuning - - -Often a speed problem can be traced to the client. The client (for -example Windows for Workgroups) can often be tuned for better TCP -performance. Check the sections on the various clients in -Samba and Other CIFS Clients. - - - - - -Samba Performance Problem Due to Changing Linux Kernel - - -A user wrote the following to the mailing list: - - -
- -Gentoo -slow network -I am running Gentoo on my server and Samba 2.2.8a. Recently I changed kernel versions from -linux-2.4.19-gentoo-r10 to linux-2.4.20-wolk4.0s. Now I have a -performance issue with Samba. Many of you will probably say, Move to vanilla sources! Well, I -tried that and it didn't work. I have a 100MB LAN and two computers (Linux and Windows 2000). The Linux server -shares directories with DivX files, the client (Windows 2000) plays them via LAN. Before, when I was running -the 2.4.19 kernel, everything was fine, but now movies freeze and stop. I tried moving files between the -server and Windows, and it is terribly slow. - -
- - -The answer he was given is: - - -
- -ifconfig -framing error -collisions -Grab the mii-tool and check the duplex settings on the NIC. My guess is that it is a link layer issue, not an -application layer problem. Also run ifconfig and verify that the framing error, collisions, and so on, look -normal for ethernet. - -
- - - - -Corrupt tdb Files - - -PDC -mbd kept spawning -/var/locks/*.tdb -Our Samba PDC server has been hosting three TB of data to our 500+ users [Windows NT/XP] for the last three -years using Samba without a problem. Today all shares went very slow. Also, the main smbd kept spawning new -processes, so we had 1600+ running SMDB's (normally we average 250). It crashed the SUN E3500 cluster twice. -After a lot of searching, I decided to rm /var/locks/*.tdb. Happy again. - - - -Question: Is there any method of keeping the *.tdb files in top condition, or -how can I detect early corruption? - - - -tdbbackup -nmbd -Answer: Yes, run tdbbackup each time after stopping nmbd and before starting nmbd. - - - -Question: What I also would like to mention is that the service latency seems -a lot lower than before the locks cleanup. Any ideas on keeping it top notch? - - - -Answer: Yes. Same answer as for previous question! - - - - - -Samba Performance is Very Slow - - -slow performance -A site reported experiencing very baffling symptoms with MYOB Premier opening and -accessing its data files. Some operations on the file would take between 40 and -45 seconds. - - - -printer monitor -pauses -It turned out that the printer monitor program running on the Windows -clients was causing the problems. From the logs, we saw activity coming -through with pauses of about 1 second. - - - -networks access -printing now -Stopping the monitor software resulted in the networks access at normal -(quick) speed. Restarting the program caused the speed to slow down -again. The printer was a Canon LBP-810 and the relevant task was -something like CAPON (not sure on spelling). The monitor software -displayed a "printing now" dialog on the client during printing. - - - -We discovered this by starting with a clean install of Windows and -trying the application at every step of the installation of other software -process (we had to do this many times). - - - -Moral of the story: Check everything (other software included)! - - - - - diff --git a/docs-xml/Samba3-HOWTO/index.xml b/docs-xml/Samba3-HOWTO/index.xml index b2af47a..e496ce4 100644 --- a/docs-xml/Samba3-HOWTO/index.xml +++ b/docs-xml/Samba3-HOWTO/index.xml @@ -202,8 +202,6 @@ The chapters in this part each cover specific Samba features. - - -- 1.7.11.7 From a8e9bed744a92d57ea4dbce0d6ffa6403493a5d4 Mon Sep 17 00:00:00 2001 From: Andrew Bartlett Date: Tue, 21 May 2013 20:50:30 +1000 Subject: [PATCH 2/4] docs: Remove TOSHARG-HighAvailability which is made obsolete by CTDB This is mostly a lament on why this is hard, and while CTDB is still hard, this document tries to imply it is almost impossible, and makes no mention of the solution. Andrew Bartlett Reviewed-by: Jeremy Allison (cherry picked from commit f632150e1b5a8d8a32753f43f7433b392f3a2136) --- docs-xml/Samba3-HOWTO/TOSHARG-HighAvailability.xml | 500 --------------------- docs-xml/Samba3-HOWTO/index.xml | 2 - 2 files changed, 502 deletions(-) delete mode 100644 docs-xml/Samba3-HOWTO/TOSHARG-HighAvailability.xml diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-HighAvailability.xml b/docs-xml/Samba3-HOWTO/TOSHARG-HighAvailability.xml deleted file mode 100644 index 1ce81d4..0000000 --- a/docs-xml/Samba3-HOWTO/TOSHARG-HighAvailability.xml +++ /dev/null @@ -1,500 +0,0 @@ - - - - - &author.jht; - &author.jeremy; - - -High Availability - - -Features and Benefits - - -availability -intolerance -vital task -Network administrators are often concerned about the availability of file and print -services. Network users are inclined toward intolerance of the services they depend -on to perform vital task responsibilities. - - - -A sign in a computer room served to remind staff of their responsibilities. It read: - - -
- -fail -managed by humans -economically wise -anticipate failure -All humans fail, in both great and small ways we fail continually. Machines fail too. -Computers are machines that are managed by humans, the fallout from failure -can be spectacular. Your responsibility is to deal with failure, to anticipate it -and to eliminate it as far as is humanly and economically wise to achieve. -Are your actions part of the problem or part of the solution? - -
- - -If we are to deal with failure in a planned and productive manner, then first we must -understand the problem. That is the purpose of this chapter. - - - -high availability -CIFS/SMB -state of knowledge -Parenthetically, in the following discussion there are seeds of information on how to -provision a network infrastructure against failure. Our purpose here is not to provide -a lengthy dissertation on the subject of high availability. Additionally, we have made -a conscious decision to not provide detailed working examples of high availability -solutions; instead we present an overview of the issues in the hope that someone will -rise to the challenge of providing a detailed document that is focused purely on -presentation of the current state of knowledge and practice in high availability as it -applies to the deployment of Samba and other CIFS/SMB technologies. - - - - - -Technical Discussion - - -SambaXP conference -Germany -inspired structure -The following summary was part of a presentation by Jeremy Allison at the SambaXP 2003 -conference that was held at Goettingen, Germany, in April 2003. Material has been added -from other sources, but it was Jeremy who inspired the structure that follows. - - - - The Ultimate Goal - - -clustering technologies -affordable power -unstoppable services - All clustering technologies aim to achieve one or more of the following: - - - - Obtain the maximum affordable computational power. - Obtain faster program execution. - Deliver unstoppable services. - Avert points of failure. - Exact most effective utilization of resources. - - - - A clustered file server ideally has the following properties: -clustered file server -connect transparently -transparently reconnected -distributed file system - - - - All clients can connect transparently to any server. - A server can fail and clients are transparently reconnected to another server. - All servers serve out the same set of files. - All file changes are immediately seen on all servers. - Requires a distributed file system. - Infinite ability to scale by adding more servers or disks. - - - - - - Why Is This So Hard? - - - In short, the problem is one of state. - - - - - -state information - All TCP/IP connections are dependent on state information. - - -TCP failover - The TCP connection involves a packet sequence number. This - sequence number would need to be dynamically updated on all - machines in the cluster to effect seamless TCP failover. - - - - -CIFS/SMB -TCP - CIFS/SMB (the Windows networking protocols) uses TCP connections. - - - This means that from a basic design perspective, failover is not - seriously considered. - - - All current SMB clusters are failover solutions - &smbmdash; they rely on the clients to reconnect. They provide server - failover, but clients can lose information due to a server failure. -server failure - - - - - - - Servers keep state information about client connections. - -state - CIFS/SMB involves a lot of state. - Every file open must be compared with other open files - to check share modes. - - - - - - - The Front-End Challenge - - -cluster servers -single server -TCP data streams -front-end virtual server -virtual server -de-multiplex -SMB - To make it possible for a cluster of file servers to appear as a single server that has one - name and one IP address, the incoming TCP data streams from clients must be processed by the - front-end virtual server. This server must de-multiplex the incoming packets at the SMB protocol - layer level and then feed the SMB packet to different servers in the cluster. - - - -IPC$ connections -RPC calls - One could split all IPC$ connections and RPC calls to one server to handle printing and user - lookup requirements. RPC printing handles are shared between different IPC4 sessions &smbmdash; it is - hard to split this across clustered servers! - - - - Conceptually speaking, all other servers would then provide only file services. This is a simpler - problem to concentrate on. - - - - - - Demultiplexing SMB Requests - - -SMB requests -SMB state information -front-end virtual server -complicated problem - De-multiplexing of SMB requests requires knowledge of SMB state information, - all of which must be held by the front-end virtual server. - This is a perplexing and complicated problem to solve. - - - -vuid -tid -fid - Windows XP and later have changed semantics so state information (vuid, tid, fid) - must match for a successful operation. This makes things simpler than before and is a - positive step forward. - - - -SMB requests -Terminal Server - SMB requests are sent by vuid to their associated server. No code exists today to - effect this solution. This problem is conceptually similar to the problem of - correctly handling requests from multiple requests from Windows 2000 - Terminal Server in Samba. - - - -de-multiplexing - One possibility is to start by exposing the server pool to clients directly. - This could eliminate the de-multiplexing step. - - - - - - The Distributed File System Challenge - - -Distributed File Systems - There exists many distributed file systems for UNIX and Linux. - - - -backend -SMB semantics -share modes -locking -oplock -distributed file systems - Many could be adopted to backend our cluster, so long as awareness of SMB - semantics is kept in mind (share modes, locking, and oplock issues in particular). - Common free distributed file systems include: -NFS -AFS -OpenGFS -Lustre - - - - NFS - AFS - OpenGFS - Lustre - - - -server pool - The server pool (cluster) can use any distributed file system backend if all SMB - semantics are performed within this pool. - - - - - - Restrictive Constraints on Distributed File Systems - - -SMB services -oplock handling -server pool -backend file system pool - Where a clustered server provides purely SMB services, oplock handling - may be done within the server pool without imposing a need for this to - be passed to the backend file system pool. - - - -NFS -interoperability - On the other hand, where the server pool also provides NFS or other file services, - it will be essential that the implementation be oplock-aware so it can - interoperate with SMB services. This is a significant challenge today. A failure - to provide this interoperability will result in a significant loss of performance that will be - sorely noted by users of Microsoft Windows clients. - - - - Last, all state information must be shared across the server pool. - - - - - - Server Pool Communications - - -POSIX semantics -SMB -POSIX locks -SMB locks - Most backend file systems support POSIX file semantics. This makes it difficult - to push SMB semantics back into the file system. POSIX locks have different properties - and semantics from SMB locks. - - - -smbd -tdb -Clustered smbds - All smbd processes in the server pool must of necessity communicate - very quickly. For this, the current tdb file structure that Samba - uses is not suitable for use across a network. Clustered smbds must use something else. - - - - - - Server Pool Communications Demands - - - High-speed interserver communications in the server pool is a design prerequisite - for a fully functional system. Possibilities for this include: - - - -Myrinet -scalable coherent interfaceSCI - - Proprietary shared memory bus (example: Myrinet or SCI [scalable coherent interface]). - These are high-cost items. - - - - Gigabit Ethernet (now quite affordable). - - - - Raw Ethernet framing (to bypass TCP and UDP overheads). - - - - - We have yet to identify metrics for performance demands to enable this to happen - effectively. - - - - - - Required Modifications to Samba - - - Samba needs to be significantly modified to work with a high-speed server interconnect - system to permit transparent failover clustering. - - - - Particular functions inside Samba that will be affected include: - - - - - The locking database, oplock notifications, - and the share mode database. - - - -failure semantics -oplock messages - Failure semantics need to be defined. Samba behaves the same way as Windows. - When oplock messages fail, a file open request is allowed, but this is - potentially dangerous in a clustered environment. So how should interserver - pool failure semantics function, and how should such functionality be implemented? - - - - Should this be implemented using a point-to-point lock manager, or can this - be done using multicast techniques? - - - - - - - - - A Simple Solution - - -failover servers -exported file system -distributed locking protocol - Allowing failover servers to handle different functions within the exported file system - removes the problem of requiring a distributed locking protocol. - - - -high-speed server interconnect -complex file name space - If only one server is active in a pair, the need for high-speed server interconnect is avoided. - This allows the use of existing high-availability solutions, instead of inventing a new one. - This simpler solution comes at a price &smbmdash; the cost of which is the need to manage a more - complex file name space. Since there is now not a single file system, administrators - must remember where all services are located &smbmdash; a complexity not easily dealt with. - - - -virtual server - The virtual server is still needed to redirect requests to backend - servers. Backend file space integrity is the responsibility of the administrator. - - - - - - High-Availability Server Products - - -resource failover -high-availability services -dedicated heartbeat -LAN -failover process - Failover servers must communicate in order to handle resource failover. This is essential - for high-availability services. The use of a dedicated heartbeat is a common technique to - introduce some intelligence into the failover process. This is often done over a dedicated - link (LAN or serial). - - - -SCSI -Red Hat Cluster Manager -Microsoft Wolfpack -Fiber Channel -failover communication - Many failover solutions (like Red Hat Cluster Manager and Microsoft Wolfpack) - can use a shared SCSI of Fiber Channel disk storage array for failover communication. - Information regarding Red Hat high availability solutions for Samba may be obtained from - www.redhat.com. - - - -Linux High Availability project - The Linux High Availability project is a resource worthy of consultation if your desire is - to build a highly available Samba file server solution. Please consult the home page at - www.linux-ha.org/. - - - -backend failures -continuity of service - Front-end server complexity remains a challenge for high availability because it must deal - gracefully with backend failures, while at the same time providing continuity of service - to all network clients. - - - - - - MS-DFS: The Poor Man's Cluster - - -MS-DFS -DFSMS-DFS, Distributed File Systems - MS-DFS links can be used to redirect clients to disparate backend servers. This pushes - complexity back to the network client, something already included by Microsoft. - MS-DFS creates the illusion of a simple, continuous file system name space that works even - at the file level. - - - - Above all, at the cost of complexity of management, a distributed system (pseudo-cluster) can - be created using existing Samba functionality. - - - - - - Conclusions - - - Transparent SMB clustering is hard to do! - Client failover is the best we can do today. - Much more work is needed before a practical and manageable high-availability transparent cluster solution will be possible. - MS-DFS can be used to create the illusion of a single transparent cluster. - - - - - - diff --git a/docs-xml/Samba3-HOWTO/index.xml b/docs-xml/Samba3-HOWTO/index.xml index e496ce4..66487f2 100644 --- a/docs-xml/Samba3-HOWTO/index.xml +++ b/docs-xml/Samba3-HOWTO/index.xml @@ -161,8 +161,6 @@ The chapters in this part each cover specific Samba features. - - -- 1.7.11.7 From f0c17abdf954faa0864b151f73f10cf3cbe9c5e5 Mon Sep 17 00:00:00 2001 From: Andrew Bartlett Date: Tue, 21 May 2013 20:44:26 +1000 Subject: [PATCH 3/4] docs: Fix small errors in TOSHARG-Compiling Reviewed-by: Jeremy Allison (cherry picked from commit e896f3c5bf5dee3c771985cd9dd2eb376481c22b) --- docs-xml/Samba3-HOWTO/TOSHARG-Compiling.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-Compiling.xml b/docs-xml/Samba3-HOWTO/TOSHARG-Compiling.xml index ac866a8..3a2b729 100644 --- a/docs-xml/Samba3-HOWTO/TOSHARG-Compiling.xml +++ b/docs-xml/Samba3-HOWTO/TOSHARG-Compiling.xml @@ -119,7 +119,7 @@ gpg: BAD signature from Samba Distribution Verification Key configure To build the binaries, run the program ./configure - in the top level director of the source tree. This should automatically + in the top level directory of the source tree. This should automatically configure Samba for your operating system. If you have unusual needs, then you may wish to first run: @@ -177,7 +177,7 @@ gpg: BAD signature from Samba Distribution Verification Key After you run configure, make sure that the - bin/include/config.h it generates contain lines like this: + bin/default/include/config.h it generates contain lines like this: #define HAVE_KRB5 1 #define HAVE_LDAP 1 @@ -186,7 +186,7 @@ gpg: BAD signature from Samba Distribution Verification Key If it does not, configure did not find your KRB5 libraries or - your LDAP libraries. Look in config.log to figure + your LDAP libraries. Look in bin/config.log to figure out why and fix it. -- 1.7.11.7 From 52ac08506db894e34d20eb3dccb8cd5bfe227d8a Mon Sep 17 00:00:00 2001 From: Andrew Bartlett Date: Sun, 26 May 2013 20:29:19 +1000 Subject: [PATCH 4/4] docs: Remove all references to testprns Based on debian patch documentation2.patch by Christian Perrier . This tool no longer exists in Samba. Andrew Bartlett Reviewed-by: Kai Blin (cherry picked from commit 4ae3cdcd7151237a858f668357d08ab6916bdb3b) --- docs-xml/manpages/nmbd.8.xml | 1 - docs-xml/manpages/smb.conf.5.xml | 1 - docs-xml/manpages/smbd.8.xml | 1 - docs-xml/using_samba/appd.xml | 18 ------------------ docs-xml/using_samba/ch01.xml | 6 ------ docs-xml/using_samba/ch07.xml | 8 -------- examples/tridge/smb.conf | 8 -------- 7 files changed, 43 deletions(-) diff --git a/docs-xml/manpages/nmbd.8.xml b/docs-xml/manpages/nmbd.8.xml index f666f58..0599ba3 100644 --- a/docs-xml/manpages/nmbd.8.xml +++ b/docs-xml/manpages/nmbd.8.xml @@ -266,7 +266,6 @@ 8, smb.conf 5, smbclient 1, testparm - 1, testprns 1, and the Internet RFC's rfc1001.txt, rfc1002.txt. In addition the CIFS (formerly SMB) specification is available diff --git a/docs-xml/manpages/smb.conf.5.xml b/docs-xml/manpages/smb.conf.5.xml index 44411b0..dd4f858 100644 --- a/docs-xml/manpages/smb.conf.5.xml +++ b/docs-xml/manpages/smb.conf.5.xml @@ -809,7 +809,6 @@ chmod 1770 /usr/local/samba/lib/usershares 8, smbclient 1, nmblookup 1, testparm - 1, testprns 1. diff --git a/docs-xml/manpages/smbd.8.xml b/docs-xml/manpages/smbd.8.xml index 98e76fb..0d246cd 100644 --- a/docs-xml/manpages/smbd.8.xml +++ b/docs-xml/manpages/smbd.8.xml @@ -421,7 +421,6 @@ 8, smb.conf 5, smbclient 1, testparm - 1, testprns 1, and the Internet RFC's rfc1001.txt, rfc1002.txt. In addition the CIFS (formerly SMB) specification is available diff --git a/docs-xml/using_samba/appd.xml b/docs-xml/using_samba/appd.xml index a3a23f8..018e590 100644 --- a/docs-xml/using_samba/appd.xml +++ b/docs-xml/using_samba/appd.xml @@ -1315,24 +1315,6 @@ received 6 names - -testprns - - -Thetestprns program -printersnameschecking testprns program checks a specified printer name against the system printer capabilities (printcap) file. Its command line is: - - -testprns printername [printcapname] - - -If the printcapname isn't specified, Samba attempts to use one located in the smb.conf file. If one isn't specified there, Samba will try /etc/printcap. If that fails, the program will generate an error. - - - - - - rpcclient diff --git a/docs-xml/using_samba/ch01.xml b/docs-xml/using_samba/ch01.xml index ca8bc13..01d7791 100644 --- a/docs-xml/using_samba/ch01.xml +++ b/docs-xml/using_samba/ch01.xml @@ -1375,12 +1375,6 @@ SIMPLE <1E> GROUP Registered -testprns -A program that tests whether various printers are recognized by the smbd daemon - - - - Each significant release of Samba goes through a significant exposure test before it's announced. In addition, it is quickly updated afterward if problems or unwanted side-effects are found. The latest stable distribution as of this writing is Samba 2.0.5, the long-awaited production version of Samba 2.0. This book focuses on the functionality supported in Samba 2.0, as opposed to the older 1.9.x versions of Samba, which are now obsolete. diff --git a/docs-xml/using_samba/ch07.xml b/docs-xml/using_samba/ch07.xml index 307cab7..988aab8 100644 --- a/docs-xml/using_samba/ch07.xml +++ b/docs-xml/using_samba/ch07.xml @@ -306,14 +306,6 @@ lppause command: public: true -Second, try the command testprns printername. This is a simple program that verifies that the specified printer is available in your printcap file. If your printcap file is not in the usual place, you can specify its full pathname as the second argument to the testprns command: - - -# testprns lp /etc/printcap -Looking for printer lp in printcap file /etc/printcap -Printer name lp is valid. - - Next, log on as the guest user, go to the spooling directory, and ensure that you can print using the same command that testparm says Samba will use. As mentioned before, this will tell you if you need to change the guest account, as the default account may not be allowed to print. diff --git a/examples/tridge/smb.conf b/examples/tridge/smb.conf index a2f269f..4aa40d8 100644 --- a/examples/tridge/smb.conf +++ b/examples/tridge/smb.conf @@ -31,14 +31,6 @@ print ok = yes print command = xmenu -heading "%s" OK& -[testprn] - comment = Test printer - path = /tmp - user = susan - print ok = yes - print command = cp %s /tmp/smb.%U.prn - lpq command = cat /tmp/xxyz - [amd] comment = amd area path = /mount -- 1.7.11.7