/usr/share/doc/lprng-doc/LPRng-Reference-Multipart/debugging.htm is in lprng-doc 3.8.A~rc2-3.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta name="generator" content=
"HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org">
<title>Debugging</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.79">
<link rel="HOME" title=" LPRng Reference Manual" href=
"index.htm">
<link rel="UP" title="Job Processing" href="jobsteps.htm">
<link rel="PREVIOUS" title="Forwarding Jobs" href="bk.htm">
<link rel="NEXT" title="Filters " href="filters.htm">
</head>
<body class="SECT1" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#840084" alink="#0000FF">
<div class="NAVHEADER">
<table summary="Header navigation table" width="100%" border=
"0" cellpadding="0" cellspacing="0">
<tr>
<th colspan="3" align="center">LPRng Reference Manual: 24
Sep 2004 (For LPRng-3.8.28)</th>
</tr>
<tr>
<td width="10%" align="left" valign="bottom"><a href=
"bk.htm" accesskey="P">Prev</a></td>
<td width="80%" align="center" valign="bottom">Chapter 15.
Job Processing</td>
<td width="10%" align="right" valign="bottom"><a href=
"filters.htm" accesskey="N">Next</a></td>
</tr>
</table>
<hr align="left" width="100%">
</div>
<div class="SECT1">
<h1 class="SECT1"><a name="DEBUGGING" id="DEBUGGING">15.12.
Debugging</a></h1>
<p>Options used:</p>
<ul>
<li>
<p><tt class="LITERAL">debugging=</tt><span class=
"emphasis"><i class="EMPHASIS">debugging
options</i></span></p>
</li>
<li>
<p><tt class="LITERAL">full_time</tt> FLAG <span class=
"emphasis"><i class="EMPHASIS">full or extended time
format</i></span></p>
</li>
<li>
<p><tt class="LITERAL">ms_time_resolution</tt> FLAG
<span class="emphasis"><i class="EMPHASIS">millisecond time
resolution</i></span></p>
</li>
<li>
<p><tt class="LITERAL">syslog_device=</tt><span class=
"emphasis"><i class="EMPHASIS">syslog alternative
device</i></span></p>
</li>
<li>
<p><tt class="LITERAL">use_info_cache</tt> FLAG
<span class="emphasis"><i class="EMPHASIS">cache printcap
and other information</i></span></p>
</li>
</ul>
<p>The <b class="APPLICATION">LPRng</b> software has a very
powerful debugging capability. Since most printing problems
occur on remote systems where it is impossible to run
debuggers, and since most systems do not do core dumps of
SETUID ROOT programs, the <b class="APPLICATION">LPRng</b>
software provides a very verbose set of log file trace
messages.</p>
<p>First, serious errors or other information are logged using
the <code class="FUNCTION">syslog()</code> facilities. If these
are not present on a system, then the messages are logged to
the device specified by <tt class=
"LITERAL">syslog_device</tt>.</p>
<p>For client programs, the debugging options are specified on
the command line and output is directed to <acronym class=
"ACRONYM">STDERR</acronym>. For the <b class=
"APPLICATION">lpd</b> server, debugging commands can be
specified on the command line OR as the <tt class=
"LITERAL">db=options</tt> printcap value. Output is directed to
the log file (<tt class="LITERAL">lf</tt> option value, default
log).</p>
<p>A typical debug entry has the format <tt class=
"LITERAL">2,network+1,database</tt>. This sets the general
debugging level to 2, network debugging to 1 and the database
debugging level to the default. The following debugging options
and levels are supported.</p>
<ul>
<li>
<p>nnn - general purpose debugging level</p>
</li>
<li>
<p>network - network debugging</p>
</li>
<li>
<p>database - database debugging</p>
</li>
<li>
<p>receive - job or command reception debugging</p>
</li>
<li>
<p>print - detailed job printing debugging</p>
</li>
</ul>
<p>The <tt class="LITERAL">full_time</tt> flag forces the
logging and other information which has timestamps to have a
full (year, month, day, etc.) timestamp. The <tt class=
"LITERAL">ms_time_resolution</tt> flag forces millisecond time
resolution in the time stamp.</p>
<p>The <tt class="LITERAL">use_info_cache</tt> (default ON)
causes <b class="APPLICATION">lpd</b> to cache printcap and
configuration information. This is desirable except when trying
to change values in printcap files and test the results. By
using <tt class="LITERAL">use_info_cache@</tt> in the
configuration information, you can get immediate responses.
Also, see <a href="lpcreread.htm">lpc reread</a> for another
method.</p>
</div>
<div class="NAVFOOTER">
<hr align="left" width="100%">
<table summary="Footer navigation table" width="100%" border=
"0" cellpadding="0" cellspacing="0">
<tr>
<td width="33%" align="left" valign="top"><a href="bk.htm"
accesskey="P">Prev</a></td>
<td width="34%" align="center" valign="top"><a href=
"index.htm" accesskey="H">Home</a></td>
<td width="33%" align="right" valign="top"><a href=
"filters.htm" accesskey="N">Next</a></td>
</tr>
<tr>
<td width="33%" align="left" valign="top">Forwarding
Jobs</td>
<td width="34%" align="center" valign="top"><a href=
"jobsteps.htm" accesskey="U">Up</a></td>
<td width="33%" align="right" valign="top">Filters</td>
</tr>
</table>
</div>
<p align="center"></p>
</body>
</html>
|