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

If you have an HP/UX system, IBM RS/6000 AIX computer, or Sun Solaris, example, UCX, TGV Multinet

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 21 highlights

CHAPTER 1 UNIX PRINTING The rm and rp options are not available on some UNIX systems, so if necessary check your documentation (or man pages) to determine the equivalent options. Users of Berkeley-compatible UNIX systems can use the lpc command to obtain the printer status: %lpc status laser1: queuing is enabled printing is enabled no entries no daemon present Users of AT&T-compatible UNIX systems can generally use the lpstat or rlpstat commands to obtain similar status information. Because this procedure varies from system to system, refer to your system documentation for the exact usage. 4. Skip this section if you have completed Step 3, unless you have an SCO UNIX system. If you have an HP/UX system, IBM RS/6000 AIX computer, or Sun Solaris 2.xx, there is no printcap file. This is also true for some other AT&T-based UNIX systems, as well as many VMS-based TCP/IP software packages (for example, UCX, TGV Multinet, etc.). On SCO systems, there is a printcap file, but it is automatically configured by the rlpconf command. Most of these systems generally use a printer setup program to define the service name (remote printer), the print server name (remote machine) or IP address, and the local queue name (spool directory). Refer to the appropriate section depending on your version of Unix. 1-5

  • 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-5
The rm and rp options are not available on some UNIX systems, so if necessary
check your documentation (or man pages) to determine the equivalent options.
Users of Berkeley-compatible UNIX systems can use the lpc command to obtain
the printer status:
%lpc status
laser1:
queuing is enabled
printing is enabled
no entries
no daemon present
Users of AT&T-compatible UNIX systems can generally use the lpstat or rlpstat
commands to obtain similar status information. Because this procedure varies
from system to system, refer to your system documentation for the exact usage.
4.
Skip this section if you have completed Step 3, unless you have an SCO
UNIX system.
If you have an HP/UX system, IBM RS/6000 AIX computer, or Sun Solaris
2.xx, there is no printcap file. This is also true for some other AT&T-based
UNIX systems, as well as many VMS-based TCP/IP software packages (for
example, UCX, TGV Multinet, etc.). On SCO systems, there is a printcap
file, but it is automatically configured by the rlpconf command. Most of
these systems generally use a printer setup program to define the service
name (remote printer), the print server name (remote machine) or IP address,
and the local queue name (spool directory).
Refer to the appropriate section
depending on your version of Unix.