SUMMARY: semaphores not available on reboot

From: Oscar Goldes (ogolde@impsat1.com.ar)
Date: Tue Jul 08 1997 - 10:19:44 CDT


Original question:

Hello,
Using Solaris 2.5 on a SPARC 2.4 plattform.
I have an application that uses Solaris semaphores.
I have modified the /etc/system file to reflect my needs.
However, after rebooting, it takes VERY long until the configuration can be
seen, for example, by sysdef. It will eventually take effect, however.

Executing modload /kernel/sys/semsys makes it immediately available.

My question is:
is this command executed automatically on reboot, or should it be placed in
some /rcx.d/? If that is the case, where should it be placed?
Should I use forceload instead?

The entries I have added in /etc/system are

set semsys:seminfo_semmns=70
set semsys:seminfo_semmsl=35

We attempt to get so 70 total semaphores, and 35 semaphores for each
semaphore ID.

Any help will be really appreciated!

Thanks to:
Casper Dik
Erik Janssen
Jim Harmon
Gerg Price
Caleb Warner

Answer:
>From all answers I have assembled the following:
Semaphores, as other IPC facilities, are loaded as needed. That is,
regardless of the settings in /etc/system, semaphores are loaded on first
use. The message "semaphore facility not in system", given by the ipcs
command, means that they have not been used yet, and so they have not yet
been loaded.
If the system is very short of resources, however, the load might fail.
Including a forceload directive loads them immediatly on reboot, but this
should not be necessary.

And yes, it is in the Solaris FAQ at
<http://www.wins.uva.nl/pub/solaris/solaris2/>

Oscar Goldes



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:58 CDT