From nobody@FreeBSD.ORG Fri Jun 18 15:52:22 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id B72811500A; Fri, 18 Jun 1999 15:52:22 -0700 (PDT)
Message-Id: <19990618225222.B72811500A@hub.freebsd.org>
Date: Fri, 18 Jun 1999 15:52:22 -0700 (PDT)
From: jobaldwi@vt.edu
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: [PATCH] Handbook doesn't mention default value of "mx" for /etc/printcap
X-Send-Pr-Version: www-1.0

>Number:         12284
>Category:       docs
>Synopsis:       [PATCH] Handbook doesn't mention default value of "mx" for /etc/printcap
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-doc
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jun 18 16:00:01 PDT 1999
>Closed-Date:    Sun Jul 4 14:48:47 PDT 1999
>Last-Modified:  Sun Jul  4 14:49:25 PDT 1999
>Originator:     John Baldwin
>Release:        3.2-STABLE
>Organization:
>Environment:
n/a
>Description:
Noticed by: Panagiotis Astithas <past@netmode.ntua.gr>

In its discussion of the "mx" capability for printers listed in
/etc/printcap, the Handbook section on Advanced Printing fails to
mention the default value for mx (which is mentioned in printcap(5) by
the way).  The patch below adds a little comment detailing the default
value so to not stump newbies.
>How-To-Repeat:
Be a newbie at configuring printing and wonder why print jobs over
1000K get truncated.  Or just be confused.
>Fix:
Apply this patch to: /usr/doc/en/handbook/printing/chapter.sgml

Index: chapter.sgml
===================================================================
RCS file: /usr/cvs/doc/en/handbook/printing/chapter.sgml,v
retrieving revision 1.15
diff -u -r1.15 chapter.sgml
--- chapter.sgml        1999/05/16 13:41:53     1.15
+++ chapter.sgml        1999/06/18 22:26:26
@@ -4068,7 +4068,9 @@
        <para>LPD enables you to limit the maximum byte size a file in a job
          can be with the <literal>mx</literal> capability. The units are in
          BUFSIZ blocks, which are 1024 bytes.  If you put a zero for this
-         capability, there will be no limit on file size.</para>
+         capability, there will be no limit on file size; however, if no
+         <literal>mx</literal> capability is specified, then a default limit
+         of 1000 blocks will be used.</para>
 
        <note>
          <para>The limit applies to <emphasis>files</emphasis> in a job, and


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: nik 
State-Changed-When: Sun Jul 4 14:48:47 PDT 1999 
State-Changed-Why:  
Fix applied, thanks. 
>Unformatted:
