/share/doc/smm/07.lpd/7.t

https://bitbucket.org/freebsd/freebsd-head/ · Raku · 226 lines · 226 code · 0 blank · 0 comment · 8 complexity · 72b0d68554378b94694582cb465bb9fe MD5 · raw file

  1. .\" Copyright (c) 1983, 1993
  2. .\" The Regents of the University of California. All rights reserved.
  3. .\"
  4. .\" Redistribution and use in source and binary forms, with or without
  5. .\" modification, are permitted provided that the following conditions
  6. .\" are met:
  7. .\" 1. Redistributions of source code must retain the above copyright
  8. .\" notice, this list of conditions and the following disclaimer.
  9. .\" 2. Redistributions in binary form must reproduce the above copyright
  10. .\" notice, this list of conditions and the following disclaimer in the
  11. .\" documentation and/or other materials provided with the distribution.
  12. .\" 3. All advertising materials mentioning features or use of this software
  13. .\" must display the following acknowledgement:
  14. .\" This product includes software developed by the University of
  15. .\" California, Berkeley and its contributors.
  16. .\" 4. Neither the name of the University nor the names of its contributors
  17. .\" may be used to endorse or promote products derived from this software
  18. .\" without specific prior written permission.
  19. .\"
  20. .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
  21. .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
  22. .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
  23. .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
  24. .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
  25. .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
  26. .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
  27. .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
  28. .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
  29. .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
  30. .\" SUCH DAMAGE.
  31. .\"
  32. .\" @(#)7.t 8.1 (Berkeley) 6/8/93
  33. .\"
  34. .NH 1
  35. Troubleshooting
  36. .PP
  37. There are several messages that may be generated by the
  38. the line printer system. This section
  39. categorizes the most common and explains the cause
  40. for their generation. Where the message implies a failure,
  41. directions are given to remedy the problem.
  42. .PP
  43. In the examples below, the name
  44. .I printer
  45. is the name of the printer from the
  46. .I printcap
  47. database.
  48. .NH 2
  49. LPR
  50. .SH
  51. lpr: \fIprinter\fP\|: unknown printer
  52. .IP
  53. The
  54. .I printer
  55. was not found in the
  56. .I printcap
  57. database. Usually this is a typing mistake; however, it may indicate
  58. a missing or incorrect entry in the /etc/printcap file.
  59. .SH
  60. lpr: \fIprinter\fP\|: jobs queued, but cannot start daemon.
  61. .IP
  62. The connection to
  63. .I lpd
  64. on the local machine failed.
  65. This usually means the printer server started at
  66. boot time has died or is hung. Check the local socket
  67. /dev/printer to be sure it still exists (if it does not exist,
  68. there is no
  69. .I lpd
  70. process running).
  71. Usually it is enough to get a super-user to type the following to
  72. restart
  73. .IR lpd .
  74. .DS
  75. % /usr/lib/lpd
  76. .DE
  77. You can also check the state of the master printer daemon with the following.
  78. .DS
  79. % ps l`cat /usr/spool/lpd.lock`
  80. .DE
  81. .IP
  82. Another possibility is that the
  83. .I lpr
  84. program is not set-user-id to \fIroot\fP, set-group-id to group \fIdaemon\fP.
  85. This can be checked with
  86. .DS
  87. % ls \-lg /usr/ucb/lpr
  88. .DE
  89. .SH
  90. lpr: \fIprinter\fP\|: printer queue is disabled
  91. .IP
  92. This means the queue was turned off with
  93. .DS
  94. % lpc disable \fIprinter\fP
  95. .DE
  96. to prevent
  97. .I lpr
  98. from putting files in the queue. This is normally
  99. done by the system manager when a printer is
  100. going to be down for a long time. The
  101. printer can be turned back on by a super-user with
  102. .IR lpc .
  103. .NH 2
  104. LPQ
  105. .SH
  106. waiting for \fIprinter\fP to become ready (offline ?)
  107. .IP
  108. The printer device could not be opened by the daemon.
  109. This can happen for several reasons,
  110. the most common is that the printer is turned off-line.
  111. This message can also be generated if the printer is out
  112. of paper, the paper is jammed, etc.
  113. The actual reason is dependent on the meaning
  114. of error codes returned by system device driver.
  115. Not all printers supply enough information
  116. to distinguish when a printer is off-line or having
  117. trouble (e.g. a printer connected through a serial line).
  118. Another possible cause of this message is
  119. some other process, such as an output filter,
  120. has an exclusive open on the device. Your only recourse
  121. here is to kill off the offending program(s) and
  122. restart the printer with
  123. .IR lpc .
  124. .SH
  125. \fIprinter\fP is ready and printing
  126. .IP
  127. The
  128. .I lpq
  129. program checks to see if a daemon process exists for
  130. .I printer
  131. and prints the file \fIstatus\fP located in the spooling directory.
  132. If the daemon is hung, a super user can use
  133. .I lpc
  134. to abort the current daemon and start a new one.
  135. .SH
  136. waiting for \fIhost\fP to come up
  137. .IP
  138. This implies there is a daemon trying to connect to the remote
  139. machine named
  140. .I host
  141. to send the files in the local queue.
  142. If the remote machine is up,
  143. .I lpd
  144. on the remote machine is probably dead or
  145. hung and should be restarted as mentioned for
  146. .IR lpr .
  147. .SH
  148. sending to \fIhost\fP
  149. .IP
  150. The files should be in the process of being transferred to the remote
  151. .IR host .
  152. If not, the local daemon should be aborted and started with
  153. .IR lpc .
  154. .SH
  155. Warning: \fIprinter\fP is down
  156. .IP
  157. The printer has been marked as being unavailable with
  158. .IR lpc .
  159. .SH
  160. Warning: no daemon present
  161. .IP
  162. The \fIlpd\fP process overseeing
  163. the spooling queue, as specified in the ``lock'' file
  164. in that directory, does not exist. This normally occurs
  165. only when the daemon has unexpectedly died.
  166. The error log file for the printer and the \fIsyslogd\fP logs
  167. should be checked for a
  168. diagnostic from the deceased process.
  169. To restart an \fIlpd\fP, use
  170. .DS
  171. % lpc restart \fIprinter\fP
  172. .DE
  173. .SH
  174. no space on remote; waiting for queue to drain
  175. .IP
  176. This implies that there is insufficient disk space on the remote.
  177. If the file is large enough, there will never be enough space on
  178. the remote (even after the queue on the remote is empty). The solution here
  179. is to move the spooling queue or make more free space on the remote.
  180. .NH 2
  181. LPRM
  182. .SH
  183. lprm: \fIprinter\fP\|: cannot restart printer daemon
  184. .IP
  185. This case is the same as when
  186. .I lpr
  187. prints that the daemon cannot be started.
  188. .NH 2
  189. LPD
  190. .PP
  191. The
  192. .I lpd
  193. program can log many different messages using \fIsyslogd\fP\|(8).
  194. Most of these messages are about files that can not
  195. be opened and usually imply that the
  196. .I printcap
  197. file or the protection modes of the files are
  198. incorrect. Files may also be inaccessible if people
  199. manually manipulate the line printer system (i.e. they
  200. bypass the
  201. .I lpr
  202. program).
  203. .PP
  204. In addition to messages generated by
  205. .IR lpd ,
  206. any of the filters that
  207. .I lpd
  208. spawns may log messages using \fIsyslogd\fP or to the error log file
  209. (the file specified in the \fBlf\fP entry in \fIprintcap\fP\|).
  210. .NH 2
  211. LPC
  212. .PP
  213. .SH
  214. couldn't start printer
  215. .IP
  216. This case is the same as when
  217. .I lpr
  218. reports that the daemon cannot be started.
  219. .SH
  220. cannot examine spool directory
  221. .IP
  222. Error messages beginning with ``cannot ...'' are usually because of
  223. incorrect ownership or protection mode of the lock file, spooling
  224. directory or the
  225. .I lpc
  226. program.