Internet Express for Tru64 UNIX Version 6.8 Administration Guide (14233)

2. The requested shared memory segment was too small for your system.
You need to lower the SHMMIN parameter in your kernel.
3. The requested shared memory segment already exists but is of the
wrong size. This is most likely the case if an old version of
PostgreSQL crashed and didn't clean up. The `ipcclean' utility
can be used to remedy this.
The PostgreSQL Administrator's Guide contains more information about
shared memory configuration.
b. The actual numbers reported in the error message will be different. You will need to
modify the parameters in your kernel, and in the shm_max and sem_mni values, as
follows:
1) Determine the appropriate shm_max value. This should be the number of bytes
reported in the error message (in this example, 28901376).
2) Determine the appropriate sem_mni value. It should be greater than
max_connections / 16. (For example, if max_connections is set to 512, then
sem_mni will need to be greater than 32. Set it to 33 or higher.)
3) Change the following values:
Create a small file named, for example, ipc.stanza and use the appropriate
values. For example:
ipc:
shm_max=28901376
sem_mni=33
4) Execute:
#/sbin/sysconfigdb -m -f ipc.stanza
5) Assure that the ipc parameters were added:
# tail /etc/sysconfigtab
6. Reboot the system.
After rebooting, you can check that the changes have taken effect by this command:
#/sbin/sysconfig -q ipc
PostgreSQL will also start. Confirm that PostgreSQL is running by this command:
#ps -ef | grep postmaster.
If the postmaster process still did not start, review the
/usr/internet/pgsql/data/postmaster.log file for an error message.
For information on what may be causing the error, review the PostgreSQL documentation
at http://www.postgresql.org or from the installed documentation in the
/usr/internet/pgsql/docs directory.
17.7 Administering MySQL
This section describes the files and processes initiated by the MySQL installation, related scripts,
and MySQL configuration files and log files.
You can use the Administration utility to performs the following tasks with My SQL:
Start or stop MySQL (see Section 17.7.2)
View the MySQL Error Log (see Section 17.7.6)
View the MySQL General Log (see Section 17.7.7)
17.7 Administering MySQL 261