Brother International HL-1870n Network Users Manual - English - Page 20

Users of RS/6000 AIX, Appendix B, SCO UNIX Configuration

Get Brother International HL-1870n PDF manuals and user guides View all Brother International HL-1870n manuals
Add to My Manuals
Save this manual to your list of manuals

Page 20 highlights

CHAPTER 1 UNIX PRINTING Choose one of the available services (a service name will be used in step 3): BINARY_P1 Binary data TEXT_P1 Text data (CR added) You may set up multiple print queues on your UNIX host computer for the same print server, each one with a different service name (for example, one queue for binary graphics jobs and one for text jobs). Refer to Appendix B for additional information on using services. 3. Configure the /etc/printcap file on each host computer to specify the local print queue, the print server name (also called remote machine or rm), and the print server service name (also called remote printer, remote queue, or rp), and the spool directory. This step applies to the majority of UNIX systems, including Linux, Sun OS (but not Solaris 2.xx), Silicon Graphics (lpr/lpd option required), DEC ULTRIX, DEC OSF/1, and Digital UNIX. SCO UNIX users should follow these steps, but should also refer to the SCO UNIX Configuration section. Users of RS/6000 AIX, HP/UX, Sun Solaris 2.xx, and other systems that do not use the printcap file should skip to section 3-a. SCO user's should also skip to section 3a (SCO uses the printcap file, but this file is automatically configured via the rlpconf command) An example of a typical printcap file: laser1|Printer on Floor 1:\ :lp=:\ :rm=BRN_310107:\ :rp=TEXT_P1:\ :sd=/usr/spool/lpd/laser1: Make sure this information is added to the end of the printcap file. Also make sure that the last character in the printcap file is a colon ":" This will create a queue named laser1 on the host computer that communicates to a Brother print server with a node name (rm) of BRN_310107 and a service name (rp) of TEXT_P1 printing text files to a Brother printer through spool directory /usr/spool/lpd/laser1. If you are printing binary graphics files, you would use the service BINARY_P1 instead of TEXT_P1. 1-4

  • 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
CHAPTER 1 UNIX PRINTING
1-4
Choose one of the available services (a service name will be used in step 3):
BINARY_P1
Binary data
TEXT_P1
Text data (CR added)
You may set up multiple print queues on your UNIX host computer for
the same print server, each one with a different service name (for
example, one queue for binary graphics jobs and one for text jobs). Refer
to
Appendix B
for additional information on using services.
3.
Configure the
/etc/printcap
file on each host computer to specify
the local print queue, the print server name (also called remote machine
or rm), and the print server service name (also called remote printer,
remote queue, or rp), and the spool directory.
This step applies to the majority of UNIX systems, including Linux, Sun OS (but
not Solaris 2.xx), Silicon Graphics (lpr/lpd option required), DEC ULTRIX,
DEC OSF/1, and Digital UNIX. SCO UNIX users should follow these steps, but
should also refer to the
SCO UNIX Configuration
section. Users of RS/6000 AIX,
HP/UX, Sun Solaris 2.xx, and other systems that do not use the printcap file
should skip to section 3-a. SCO user’s should also skip to section 3a (SCO uses
the printcap file, but this file is automatically configured via the
rlpconf
command)
An example of a typical printcap file:
laser1|Printer on Floor 1:\
:lp=:\
:rm=BRN_310107:\
:rp=TEXT_P1:\
:sd=/usr/spool/lpd/laser1:
Make sure this information is added to the end of the printcap file. Also make
sure that the last character in the printcap file is a colon ":"
This will create a queue named laser1 on the host computer that communicates to
a Brother print server with a node name (rm) of BRN_310107 and a service
name (rp) of TEXT_P1 printing text files to a Brother printer through spool
directory
/usr/spool/lpd/laser1
. If you are printing binary graphics files,
you would use the service BINARY_P1 instead of TEXT_P1.