Installation guide

To change the buffer size using graphical administration tools, use the
following steps:
1. Start the dxkerneltuner application.
2. Select the generic subsystem.
3. Set the Boot Time Value entry for the msgbuf_size attribute to the
new value.
4. Apply the change before exiting.
To change the buffer size from the command line, use the following steps:
1. Create a temporary file, /tmp/msgbufsize, containing the following
lines, but replacing the 32768 with the size appropriate to your system:
generic:
msgbuf_size = 32768
2. Enter the following command:
% sysconfigdb -f /tmp/msgbufsize -m
If a different entry was already present in the database, sysconfigdb
will display a warning message to advise you of the change in size.
The increase will take effect at the next system reboot. After rebooting, you
can verify the change by entering the following command:
% sysconfig -q generic | grep msgbuf_size
Note
The default size of the message buffer is 4 KB, and the example
above sets it to 32 KB. Since the space used by the buffer is not
returned for general use after initialization, you should set the
size only high enough to correct the problem.
4.3.11 Incoming Remote Print Jobs Disable Queue If They Create
spooldir Lock File
A print job to a Version 4.0F system (from any other version of Tru64
UNIX) might cause the print queue on the receiving system to become
disabled.
This occurs when the lock file is not present in the spool directory for the
queue when the remote host receives the job. This condition exists if the
print queue was newly created, or if the contents of the spool directory were
manually purged (which would delete the lock file).
When a remote job is received, the print daemon creates a lock file with a
protection mode that signifies that the queue is disabled. The initial job
Base System Software Notes 4–25