|Previous||Table of Contents||Next|
When the baud setting of the computer does not match the baud setting of the printer, you usually get some output, but it does not look like what you submitted for printing. Random characters show up, with an unusual mixture of special characters and undesirable spacing. The default for the LP print service is 9600 baud.
NOTE: If a printer is connected by a parallel port, the baud setting is irrelevant.
Some printers use a parity bit to ensure that data received for printing has not been garbled during transmission. The parity bit settings for the computer and for the printer must match. If they do not match, some characters do not print at all or are replaced by other characters. The output will look only approximately correct, with the word spacing all right and many letters in their correct place. The LP print service does not set the parity bit by default.
If tabs are set but the printer expects no tabs, the printed output may contain the complete contents of the file, but the text may be jammed against the right margin. Also, if the tab settings for the printer are incorrect, the text may not have a left margin, may run together, may be concentrated in a portion of the page, or may be incorrectly double-spaced. The default is for tab settings every eight spaces.
If the output is double-spaced but should be single-spaced, either the tab settings for the printer are incorrect or the printer is adding a line feed after each Return. The LP print service adds a Return before each line feed, so the combination causes two line feeds.
If the print zigzags down the page, the stty option onlcr, which sends a Return before every line feed, is not set. The stty=onlcr option is set by default, but you may have cleared it while trying to solve other printing problems.
If you type any of the lp commands (lpsystem, lpadmin, lpstat, lpshut) and nothing happens (you get no error message, status information, or prompt), chances are that something is wrong with the LP scheduler. You usually can resolve such a problem by stopping and restarting the LP scheduler.
Use the following steps to free hung lp commands:
# ps -e | grep lpsched 134 term/a Ø:Ø1 lpsched #
# kill -9 134 #
You may find a printer that is idle even though print requests have been queued to it. A printer may seem idle when it shouldn't be for one of the following reasons:
Slow print filters run in the background to avoid tying up the printer. A print request that requires filtering will not print until it has been filtered. To check the print filters, type lpstat -o printer-name and press Return. See if the first waiting request is being filtered. If the output looks like the following example, the file is being filtered. The printer is not hung; it just is taking a while to process the request.
pine% lpstat -o pinecone pinecone-1Ø fred 1261 Mar 12 17:34 being filtered pinecone-11 iggy 1261 Mar 12 17:36 on pine pinecone-12 jack 1261 Mar 12 17:39 on pine pine%
When the LP print service detects a fault, printing resumes automatically, but not immediately. The LP print service waits about five minutes before trying again, and continues trying until a request is printed successfully. You can force a retry immediately by enabling the printer.
Use the following steps to resume printing after a printer fault:
When printing files over a network, you may encounter the following types of problems:
Use the following steps to check that the printer is ready to print:
|Previous||Table of Contents||Next|