diff --git a/en_US.ISO8859-1/books/handbook/printing/chapter.sgml b/en_US.ISO8859-1/books/handbook/printing/chapter.sgml index 9ddd060d1f..93ebde6219 100644 --- a/en_US.ISO8859-1/books/handbook/printing/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/printing/chapter.sgml @@ -1,7 +1,7 @@ @@ -1116,8 +1116,8 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ lp capability. In our running example, let us assume that - rattan is on the first parallel port, and - bamboo is on a sixth serial port; here are + rattan is on the first parallel port, and + bamboo is on a sixth serial port; here are the additions to /etc/printcap: # @@ -1563,7 +1563,7 @@ $%&'()*+,-./01234567 - appears if the job's submitted with lpr + appears if the job is submitted with lpr -l @@ -1884,7 +1884,7 @@ if [ "$first_two_chars" = "%!" ]; then && exit 0 else # - # Plain text or HP/PCL, so just print it directly; print a form + # Plain text or HP/PCL, so just print it directly; print a form feed # at the end to eject the last page. # echo $first_line && cat && printf "\033&l0H" && @@ -2538,7 +2538,7 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\ By enabling header pages, LPD will produce a long header, a full page of large letters identifying the user, host, and job. Here is an example (kelly printed the job - named outline from host rose): + named outline from host rose): k ll ll k l l @@ -2972,13 +2972,14 @@ done Here is an example. The host rose has two printers, bamboo and rattan. - We will enable users on the host orchid to print to those printers. + We will enable users on the host orchid to print + to those printers. Here is the /etc/printcap file for orchid (back from section Enabling Header Pages). It already had the entry for the printer teak; we have added entries for the two printers - on the host rose: + on the host rose: # # /etc/printcap for host orchid - added (remote) printers on rose @@ -3014,17 +3015,18 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ Now, users on orchid can print to rattan and bamboo. If, for - example, a user on orchid typed + example, a user on orchid typed &prompt.user; lpr -P bamboo -d sushi-review.dvi - the LPD system on orchid would copy the job to the spooling - directory /var/spool/lpd/bamboo and note that - it was a DVI job. As soon as the host rose has room in its - bamboo spooling directory, the two LPDs would - transfer the file to rose. The file would wait in rose's queue - until it was finally printed. It would be converted from DVI to - PostScript (since bamboo is a PostScript printer) on rose. + the LPD system on orchid would copy the job to the spooling + directory /var/spool/lpd/bamboo and note that it was a + DVI job. As soon as the host rose has room in its + bamboo spooling directory, the two LPDs would transfer the + file to rose. The file would wait in rose's + queue until it was finally printed. It would be converted from DVI to + PostScript (since bamboo is a PostScript printer) on + rose. @@ -3138,7 +3140,7 @@ exec /usr/libexec/lpr/lpf "$@" | /usr/local/libexec/netprint scrivener 5100/etc/printcap file for the host rose. The printer rattan is quite hearty, so we will allow multiple copies, but the laser - printer bamboo's a bit more delicate, so we will + printer bamboo is a bit more delicate, so we will disable multiple copies by adding the sc capability: @@ -3376,9 +3378,9 @@ madrigal.fishbaum.de minfree file. For example, let us add a minfree - file for the printer bamboo. We examine + file for the printer bamboo. We examine /etc/printcap to find the spooling - directory for this printer; here is bamboo's + directory for this printer; here is bamboo's entry: bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ @@ -3387,14 +3389,13 @@ madrigal.fishbaum.de :if=/usr/local/libexec/psif:\ :df=/usr/local/libexec/psdf: - The spooling directory is the given in the - sd capability. We will make three - megabytes (which is 6144 disk blocks) the amount of free disk - space that must exist on the filesystem for LPD to accept - remote jobs: + The spooling directory is given in the sd + capability. We will make three megabytes (which is 6144 disk blocks) + the amount of free disk space that must exist on the filesystem for + LPD to accept remote jobs: - &prompt.root; echo 6144 > /var/spool/lpd/bam -boo/minfree + &prompt.root; echo 6144 > /var/spool/lpd/bamboo/minfree + @@ -3417,7 +3418,7 @@ boo/minfree giving them accounts on your systems, they can use your printers from their own departmental systems. If you would rather allow them to use only your - printers and not your compute resources, you can give them + printers and not your computer resources, you can give them token accounts, with no home directory and a useless shell like /usr/bin/false. @@ -3524,8 +3525,8 @@ boo/minfree You should use a separate accounting file for each printer, as lpf has no file locking logic built into it, and two lpfs might corrupt each other's entries if - they were to write to the same file at the same time. A easy way to - insure a separate accounting file for each printer is to use + they were to write to the same file at the same time. An easy way + to insure a separate accounting file for each printer is to use af=acct in /etc/printcap. Then, each accounting file will be in the spooling directory for a printer, in a file named acct. @@ -3821,7 +3822,7 @@ total 337.00 154 $ 6.74 &prompt.user; lpq -P bamboo - shows the queue for the printer named bamboo. Here + shows the queue for the printer named bamboo. Here is an example of the output of the lpq command: @@ -3845,7 +3846,7 @@ active kelly 9 /etc/host.conf, /etc/hosts.equiv 88 bytes be currently printing that job. The second job consists of data passed as the standard input to the &man.lpr.1; command. The third job came from user mary; it is a much larger - job. The pathname of the files she's trying to print is too long to + job. The pathname of the file she is trying to print is too long to fit, so the &man.lpq.1; command just shows three dots. The very first line of the output from &man.lpq.1; is also useful: @@ -3883,7 +3884,7 @@ mary: 3rd [job 011rose] To remove the job from a specific printer, add the option. The following command removes job number - 10 from the queue for the printer bamboo: + 10 from the queue for the printer bamboo: &prompt.user; lprm -P bamboo 10 @@ -4277,7 +4278,7 @@ cfA013rose dequeued to get printer status and to restart a hung printer only. Here is a summary of the &man.lpc.8; commands. Most of the - commands takes a printer-name argument to + commands take a printer-name argument to tell on which printer to operate. You can use all for the printer-name to mean all printers listed in /etc/printcap. @@ -4289,7 +4290,7 @@ cfA013rose dequeued Cancel the current job and stop the printer. Users can - still submit jobs if the queue's enabled. + still submit jobs if the queue is enabled. @@ -4312,7 +4313,7 @@ cfA013rose dequeued printer-name - Disable queuing of new jobs. If the printer's started, it + Disable queuing of new jobs. If the printer is running, it will continue to print any jobs remaining in the queue. The superuser (root) can always submit jobs, even to a disabled queue. @@ -4608,9 +4609,9 @@ printf "\033&k2G" && cat && printf "\033&l0H" && exit 2 Here is an example /etc/printcap - from a host called orchid. It has a single printer + from a host called orchid. It has a single printer attached to its first parallel port, a Hewlett Packard - LaserJet 3Si named teak. It is using the + LaserJet 3Si named teak. It is using the above script as its text filter: #