From 09fb00c629ed81b25c97a5eb74df4e03c92145ea Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Tue, 5 Nov 2002 21:41:04 +0000 Subject: 'make everything' in docs (This used to be commit 960082d860c36419c63094be778decdadb061c1d) --- docs/htmldocs/printingdebug.html | 53 +++++++++++++++++++++++----------------- 1 file changed, 30 insertions(+), 23 deletions(-) (limited to 'docs/htmldocs/printingdebug.html') diff --git a/docs/htmldocs/printingdebug.html b/docs/htmldocs/printingdebug.html index abb83cb692..0b99407257 100644 --- a/docs/htmldocs/printingdebug.html +++ b/docs/htmldocs/printingdebug.html @@ -9,8 +9,11 @@ CONTENT="Modular DocBook HTML Stylesheet Version 1.77">Chapter 7. Debugging Printing ProblemsChapter 15. Debugging Printing Problems

7.1. Introduction

15.1. Introduction

This is a short description of how to debug printing problems with Samba. This describes how to debug problems with printing from a SMB @@ -141,7 +144,7 @@ and it should be periodically cleaned out. Samba used the lpq command to determine the "job number" assigned to your print job by the spooler.

The %>letter< are "macros" that get dynamically replaced with appropriate +>The %>letter< are "macros" that get dynamically replaced with appropriate values when they are used. The %s gets replaced with the name of the spool file that Samba creates and the %p gets replaced with the name of the printer. The %j gets replaced with the "job number" which comes from @@ -152,9 +155,9 @@ CLASS="SECT1" >

7.2. Debugging printer problems

15.2. Debugging printer problems

One way to debug printing problems is to start by replacing these command with shell scripts that record the arguments and the contents @@ -209,9 +212,9 @@ CLASS="SECT1" >

7.3. What printers do I have?

15.3. What printers do I have?

You can use the 'testprns' program to check to see if the printer name you are using is recognized by Samba. For example, you can @@ -238,9 +241,9 @@ CLASS="SECT1" >

7.4. Setting up printcap and print servers

15.4. Setting up printcap and print servers

You may need to set up some printcaps for your Samba system to use. It is strongly recommended that you use the facilities provided by @@ -322,9 +325,9 @@ CLASS="SECT1" >

7.5. Job sent, no output

15.5. Job sent, no output

This is the most frustrating part of printing. You may have sent the job, verified that the job was forwarded, set up a wrapper around @@ -367,9 +370,9 @@ CLASS="SECT1" >

7.6. Job sent, strange output

15.6. Job sent, strange output

Once you have the job printing, you can then start worrying about making it print nicely.

7.7. Raw PostScript printed

15.7. Raw PostScript printed

This is a problem that is usually caused by either the print spooling system putting information at the start of the print job that makes @@ -428,9 +431,9 @@ CLASS="SECT1" >

7.8. Advanced Printing

15.8. Advanced Printing

Note that you can do some pretty magic things by using your imagination with the "print command" option and some shell scripts. @@ -444,9 +447,9 @@ CLASS="SECT1" >

7.9. Real debugging

15.9. Real debugging

If the above debug tips don't help, then maybe you need to bring in the bug guns, system tracing. See Tracing.txt in this directory.

Printing Support in Samba 2.2.xPrinting Support Up