Chapter 6: Running the Software
•
i
•
Additionally, all backchannel messages generated by a PostScript program will be
written to this file.
6-988/25/02
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
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
If you do not include the
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
flag, sdriver will not go into Debug Mode. Although
-d
UNIX Printing Software Administration and Installation Guide
flag.
-L
flag at the command line.
-d