8.5

•
The -noui option makes the server run without any user interface. This is the normal
mode for production use of QuarkXPress Server.
•
The -nonetwork parameter makes the server run without loading any network interfaces;
in this mode, the only transactions a server can run are those passed to it by another
process.
•
The -subrenders parameter lets you specify how many subrenderers to use.
•
The -tm parameter makes the transaction layer of the server mask exceptions into
transaction errors.
•
The -tt parameter makes the transaction layer of the server throw exceptions to the server
layer.
•
The -monitorsubrenders option turns on subrenderer monitoring.
To use the subrenderer monitoring feature, add the following command line parameters
to the "QuarkXPress Server.config" file:
-monitorsubrenders -queryinterval x -noofretries y -recycle
If a subrenderer process has been attempting to fulfill a request for the specified number
of retries (with the specified query interval in seconds between retries), the subrenderer
monitor recyles that process.
Windows only: If the recycle parameter is not supplied, the subrenderer monitor performs
a periodic memory check on all subrenderer processes. If the memory used by a subrenderer
process does not change within the specified number of retries with the specified query
interval, that process is recycled.
By default, the contents of the "QuarkXPress Server.config" file are as follows:
COMMANDLINE=-subrenders 1
To launch QuarkXPress Server with the options specified in the "QuarkXPress Server.config"
file, double-click the "QuarkXPress Server" icon.
Exit Codes
When the server shuts down, QuarkXPress Server returns exit codes. The "keepalive.sh"
file (Mac OS) or "keepalive.bat" file (Windows) uses these codes to check the type of
QuarkXPress Server shutdown. If the exit code indicates that QuarkXPress Server shut
down unexpectedly, the "keepalive" utilities automatically relaunch QuarkXPress Server.
Valid exit codes are as follows:
• QUARKXPRESS SERVER_EXIT_NORMAL (0): The server exited normally.
• QUARKXPRESS SERVER_EXIT_EXCEPTION (6969): The server exited as a result of an
exception that was handled by the server layer.
• QUARKXPRESS SERVER_EXIT_STARTUP (6970): The server exited as a result of a startup
problem. In this case, restarting does not solve the problem. You must relaunch QLA.
A GUIDE TO QUARKXPRESS SERVER 8.5 | 13
GETTING STARTED WITH QUARKXPRESS SERVER