|
|
1.1 ! root 1: \fBroute\fP -- MLP Spooler Command ! 2: ! 3: \fBroute\fP [destination_name] ! 4: ! 5: This command allows users to display or change their personal default ! 6: destination printer. A user's print request will print to this printer unless ! 7: specifically overridden in the \fBlp\fP or \fBlpr\fP commands. If a user does ! 8: not have a personal default, the system default destination is used instead. ! 9: ! 10: Invoking \fBroute\fP by itself displays the user's default printer followed by a list ! 11: of printers known to MLP. For example: ! 12: ! 13: main ( oki, letter, ticket, main, system, display, local ) ! 14: ! 15: would tell the user that their default is named "main" and the possible choices ! 16: include "oki," "letter," "ticket," and "main." ! 17: ! 18: To change ones' own personal default, simply give the printer's name after ! 19: \fBroute\fP on the command line. Nonexistent printers will provoke an error ! 20: message. ! 21: ! 22: There are three special predefined "printers" available. These are: \fBsystem\fP, ! 23: \fBdisplay\fP, and \fBlocal\fP. Here is what they are. ! 24: ! 25: Routing to \fBsystem\fP directs the user's requests to the current system default ! 26: destination. By routing to this "printer" the user need not be aware of how ! 27: the system's various printers are named. ! 28: ! 29: Routing to \fBdisplay\fP causes the user's request to be sent to his display rather ! 30: than an actual printer. This is useful for previewing a report. ! 31: ! 32: Routing to \fBlocal\fP causes the user's report to print on a slave printer connected ! 33: to the user's terminal. The terminal must be able to support such a printer and ! 34: the printer must exist. Also, the codes PS and PN must be defined in \fB/etc/termcap\fP ! 35: so MLP knows how to direct the data. ! 36: ! 37: Files ! 38: .br ! 39: \fB/usr/spool/mlp/route/USERNAME\fP -- MLP user preferences ! 40: .br ! 41: \fB/etc/termcap\fP -- Terminal capability database ! 42:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.