1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> 2 3<html> 4 <head> 5 <meta name="generator" content="HTML Tidy, see www.w3.org"> 6 <title>What is RFC 1179, the Line Printer Daemon 7 Protocol?</title> 8 <meta name="GENERATOR" content= 9 "Modular DocBook HTML Stylesheet Version 1.7"> 10 <link rel="HOME" title=" LPRng Reference Manual" href= 11 "index.htm"> 12 <link rel="UP" title="The Most Frequently Asked Questions " 13 href="faq.htm"> 14 <link rel="PREVIOUS" title= 15 "I get messages about bad control file format" href= 16 "x10807.htm"> 17 <link rel="NEXT" title= 18 "I want to replace lp, lpstat, etc, but my programs need them" 19 href="x10839.htm"> 20 </head> 21 22 <body class="SECT1" bgcolor="#FFFFFF" text="#000000" link= 23 "#0000FF" vlink="#840084" alink="#0000FF"> 24 <div class="NAVHEADER"> 25 <table summary="Header navigation table" width="100%" border= 26 "0" cellpadding="0" cellspacing="0"> 27 <tr> 28 <th colspan="3" align="center">LPRng Reference Manual: 5 29 Sep 2003 (For LPRng-3.8.22)</th> 30 </tr> 31 32 <tr> 33 <td width="10%" align="left" valign="bottom"><a href= 34 "x10807.htm" accesskey="P">Prev</a></td> 35 36 <td width="80%" align="center" valign="bottom">Chapter 37 20. The Most Frequently Asked Questions</td> 38 39 <td width="10%" align="right" valign="bottom"><a href= 40 "x10839.htm" accesskey="N">Next</a></td> 41 </tr> 42 </table> 43 <hr align="LEFT" width="100%"> 44 </div> 45 46 <div class="SECT1"> 47 <h1 class="SECT1"><a name="RFC1179">20.6. What is RFC 1179, 48 the Line Printer Daemon Protocol?</a></h1> 49 50 <p>RFC1179 defines a standard method by which print jobs can 51 be transferred using the TCP/IP protocol between hosts. The 52 standard was developed by simply detailing the way that a 53 version of the BSD <b class="APPLICATION">lpd</b> software 54 did its job.</p> 55 56 <p>From the RFC Introduction: <a name="AEN10820"></a></p> 57 58 <blockquote class="BLOCKQUOTE"> 59 <p>RFC 1179 describes a print server protocol widely used 60 on the Internet for communicating between line printer 61 daemons (both clients and servers). RFC1179 is for 62 informational purposes only, and does not specify an 63 Internet standard.</p> 64 </blockquote> 65 <br> 66 <br> 67 68 <p>Having said this, the RFC then goes on to describe the 69 protocol used by a particular implementation of <b class= 70 "APPLICATION">lpd</b>. The problem was that the RFC did not 71 provide any way to put extensions to the operations into the 72 system, and failed to specify such interesting details as the 73 order in which print jobs and their components could be 74 transferred.</p> 75 76 <p>Comment by Patrick Powell <var class= 77 "LITERAL"><papowell@lprng.com></var> : <a name= 78 "AEN10826"></a></p> 79 80 <blockquote class="BLOCKQUOTE"> 81 <p>Since 1988, there have been a large number of print 82 spooling systems developed which claim RFC1179 conformance, 83 but which are mutually incompatible.</p> 84 85 <p>Rather than live with the limited capabilities of the 86 RFC1179 standard, <b class="APPLICATION">LPRng</b> has 87 extended them by adding capabilities to perform remote 88 control of print spoolers, encrypted and authenticated data 89 transfers, and other operations missing from the RFC1179 90 specification. However, great effort was made to be 91 backwards compatible with older and other <b class= 92 "APPLICATION">lpd</b> based systems.</p> 93 94 <p><b class="APPLICATION">LPRng</b> was developed in order 95 to be able to both accept and provide interactions with 96 these systems. It does so by allowing various options to be 97 used to <span class="emphasis"><i class= 98 "EMPHASIS">tune</i></span> how print jobs would be 99 exchanged. Currently, <b class="APPLICATION">LPRng</b> can 100 be configured to send and receive print jobs between a vast 101 number of the existing spooling systems. It is flexible 102 enough to act as a gateway between non-compatible systems, 103 and has provisions to transform jobs from one format to 104 another in a dynamic manner.</p> 105 </blockquote> 106 <br> 107 <br> 108 109 <p>For a detailed explanation about <b class= 110 "APPLICATION">LPRng</b> and RFC1179, see <a href= 111 "rfc1179ref.htm">RFC1179 and <b class= 112 "APPLICATION">LPRng</b></a>.</p> 113 </div> 114 115 <div class="NAVFOOTER"> 116 <hr align="LEFT" width="100%"> 117 118 <table summary="Footer navigation table" width="100%" border= 119 "0" cellpadding="0" cellspacing="0"> 120 <tr> 121 <td width="33%" align="left" valign="top"><a href= 122 "x10807.htm" accesskey="P">Prev</a></td> 123 124 <td width="34%" align="center" valign="top"><a href= 125 "index.htm" accesskey="H">Home</a></td> 126 127 <td width="33%" align="right" valign="top"><a href= 128 "x10839.htm" accesskey="N">Next</a></td> 129 </tr> 130 131 <tr> 132 <td width="33%" align="left" valign="top">I get messages 133 about bad control file format</td> 134 135 <td width="34%" align="center" valign="top"><a href= 136 "faq.htm" accesskey="U">Up</a></td> 137 138 <td width="33%" align="right" valign="top">I want to 139 replace lp, lpstat, etc, but my programs need them</td> 140 </tr> 141 </table> 142 </div> 143 </body> 144</html> 145 146