User manual

User’s Manual InterCon-PrintServer
85
Example: To load the shellscript for systemV UNIX:
ftp> get sys5.sh
200 PORT command successful.
150 ASCII data connection for sys5.sh (192.168.0.49,1035).
226 Transfer complete.
15700 bytes received in 0.38 seconds (41.32 Kbytes/sec)
ftp> quit
221 Goodbye.
The
*.sh
files are prime examples of standard printer interfaces of the print spoolers
lpsched
,
lpd
and
qdaemon
supported by the print server. All adjusted printer interfaces of the installed print
servers have to be copied into the
/etc/printserver/interfaces
subdirectory.
All log files of the last print job are stored in the
/tmp
subdirectory. In case of an error the
information contained in the log file can give you some clues as to what may have caused the problem.
After all said parameters have been assigned and all directories created, you can start the print server
installation. This installation is divided into two parts. First, the print server will be installed as a
TCP/IP-Host in your local network. After this, one or more network printers will be added to your
print spooler system.
7.10.2 Description of the Printer Interfaces
All included printer interfaces (shellscripts) for connecting the print server into the UNIX spooler
system should be seen as prime examples and therefore have to be adjusted to your UNIX systems
environment.
This section describes the basic functions of these scripts.
Some variables are initialised at the beginning of the scripts. These variables are described below.
A protocol file which is named after the printer with the ending
.last
, is stored in the
/tmp
directory. This file contains a protocol of the print job, e.g. starting time of the print job, parameters
for addressing the printer interface and the FTP commands.
Depending on the spooler system, all data to be printed will be transmitted via the standard input
channel to the script, or the name of the file to be printed will be transmitted to the script as a
parameter.
A bannerpage is created in the scripts. This depends on the
nobanner
variable, which is initialised
by
no
. This variable may be set to
yes
by the option
-o nobanner
in the
lp
command.
✘ ✘
This bannerpage is not postscript compatible. If a postscript printer is connected, the printout
of the bannerpage has to be suppressed. Do so by initialising the nobanner variable
with yes . The
nofilebreak
variable also has to be initialised
yes
for postscript printers.