Brother International HL-7050N Network Users Manual - English - Page 21

Sun Solaris 2.x Configuration, 10 UNIX PRINTING

Get Brother International HL-7050N PDF manuals and user guides
UPC - 012502603375
View all Brother International HL-7050N manuals
Add to My Manuals
Save this manual to your list of manuals

Page 21 highlights

Sun Solaris 2.x Configuration Sun Solaris 2.x uses the lpsystem and lpadmin programs for remote printer configuration: lpsystem -t bsd prnservername lpadmin -p queue -s prnservername!prnserverservice accept queue (not required on newer Solaris systems) enable queue (not required on newer Solaris systems) Where queue is the name of the local print queue. prnservername is the name of the print server (must match the entry in the /etc/hosts file or IP address). prnserverservice is the print server BINARY_P1 or TEXT_P1 service. If this is the first printer configured, you must also use the lpsched command prior to the accept command. As an alternative, you may use Printer Manager in the Admintool utility under OpenWindows. Select Edit, Add, and Add Access to Remote Printer. Then enter the print server name in the format prnservername!\prnserverservice as described above. Make sure that the printer server OS is set to BSD (the default setting), and click Add. Note that we recommend that you use the /etc/hosts file for the printer name rather than NIS or other name services. Also note that due to a bug in the Sun lpd implementation on Solaris 2.4 and earlier releases, you may experience problems printing very long print jobs. If this is the case, a workaround is to use the raw TCP port software as described later in this chapter. 1 - 10 UNIX PRINTING

  • 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
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
1 - 10 UNIX PRINTING
Sun Solaris 2.x Configuration
Sun Solaris 2.x uses the lpsystem and lpadmin programs for remote
printer configuration:
lpsystem -t bsd prnservername
lpadmin -p queue -s prnservername!prnserverservice
accept queue
(not required on newer Solaris systems)
enable queue
(not required on newer Solaris systems)
Where
queue
is the name of the local print queue.
prnservername
is the name of the print server (must match the
entry in the
/etc/hosts
file or IP address).
prnserverservice
is the print server BINARY_P1 or TEXT_P1
service.
If this is the first printer configured, you must also use the
lpsched
command prior to the
accept
command.
As an alternative, you may use Printer Manager in the Admintool
utility under OpenWindows. Select
Edit
,
Add
, and
Add Access to
Remote Printer
. Then enter the print server name in the format
prnservername!\prnserverservice
as described above.
Make sure that the printer server OS is set to
BSD
(the default
setting), and click
Add
.
Note that we recommend that you use the
/etc/hosts
file for the
printer name rather than NIS or other name services. Also note that
due to a bug in the Sun lpd implementation on Solaris 2.4 and earlier
releases, you may experience problems printing very long print jobs.
If this is the case, a workaround is to use the raw TCP port software
as described later in this chapter.