Technical data

The /sbin/init.d/apx start and /sbin/init.d/apx stop commands
start and stop the LPD Inbound Gateway.
5.4 Managing Servers
This section describes the administrative tasks that you perform on spoolers
and supervisors. These tasks include starting and stopping, pausing and
resuming, enabling and disabling, and possibly deleting servers.
5.4.1 Server States
The server attributes server-state and enabled determine the state of a
server process. The server process can be in one of the following states:
• ready — The server is available to accept print jobs. This is the normal
operating state of the server.
• terminating — The server is in the process of shutting down and exiting.
• paused — The server has been paused and will not accept jobs until the
server is resumed.
While server-state can be set to ready, if the server is disabled, it will
not receive print jobs.
Use the following command line to determine the state of a server, in this
case blue_sup:
# pdls -c server blue_sup
The default for this command returns both the server-state and the
enabled attributes:
server-name server-state enabled
----------- ------------ ------------
blue_sup ready yes
5.4.2 Starting a Server
Starting a server consists of running an appropriate executable file for the
server type. The startup syntax represents a string that you can type at a
shell prompt. Generally, however, you will start servers by way of a shell
script, and the host will execute the startup syntax from within the shell
script. The shell script could be part of the startup script that you create or
the one that executes normally when the UNIX system boots, such as the
file /sbin/init.d/apx or a CAA action script.
A print system server behaves like a UNIX daemon. It starts up at boot time
by way of a shell script without user input. Like typical UNIX daemons, the
5–14 Creating and Managing Servers