Oki B6100n Guide: Administration and Installation, B6100 UNIX Printing Softwar - Page 104

enter Debug Mode., Error Logs

Get Oki B6100n PDF manuals and user guides View all Oki B6100n manuals
Add to My Manuals
Save this manual to your list of manuals

Page 104 highlights

Chapter 6: Running the Software stdin. The user's file is then passed from the spooler through sdriver and on to the printer. • Event files (optional). To set up sdriver to log an event file of all of the output data returned by the printer over the raw TCP/IP socket, include the -L flag. i In order for the sdriver to be able to open an event file, the printer must be attached to a bi-directional port. If sdriver is attached to a uni-directional port, the event file will still open, but no data will stored. • Error Logs To set up the sdriver to log all printer communicating errors to a log file, you must enter Debug Mode. You do this by entering the -d flag at the command line. If you do not include the -d flag, sdriver will not go into Debug Mode. Although sdriver will still log to your log file, it will only provide the illegal number of input parameters message. The following is a list of error conditions that sdriver will report while in Debug Mode: • Invalid number of arguments entered by user • Socket creation failure • Socket open failure • gethostbyname failure (printer name not in /etc/hosts) on DNS database. • Connect failure • Read from stdin failure • Send data to printer failure • Shutdown socket failure Additionally, all backchannel messages generated by a PostScript program will be written to this file. 6-988/25/02 UNIX Printing Software Administration and Installation Guide

  • 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
6-98
8/25/02
UNIX Printing Software Administration and Installation Guide
Chapter 6: Running the Software
stdin. The user’s file is then passed from the spooler through sdriver and on to the
printer.
•
Event files (optional).
To set up sdriver to log an event file of all of the output data returned by the
printer over the raw TCP/IP socket, include the
-L
flag.
•
Error Logs
To set up the sdriver to log all printer communicating errors to a log file, you must
enter Debug Mode.
You do this by entering the
-d
flag at the command line.
If you do not include the
-d
flag, sdriver will not go into Debug Mode.
Although
sdriver will still log to your log file, it will only provide the illegal number of
input parameters message.
The following is a list of error conditions that sdriver will report while in Debug
Mode:
•
Invalid number of arguments entered by user
•
Socket creation failure
•
Socket open failure
•
gethostbyname failure (printer name not in /etc/hosts) on DNS database.
•
Connect failure
•
Read from stdin failure
•
Send data to printer failure
•
Shutdown socket failure
Additionally, all backchannel messages generated by a PostScript program will be
written to this file.
i
In order for the sdriver to be able to open an event file, the printer must be
attached to a bi-directional port.
If sdriver is attached to a uni-directional port,
the event file will still open, but no data will stored.