CURRENT on Solaris - another problem?

[Russ Allbery]

Przemys=B3aw Maciuszko <sal at agora.pl> writes:

> I've just upgraded to latest CURRENT and i get the following in news.noti=
ce:
> Jan 27 23:54:00 inews nnrpd[8051]: [ID 223153 news.error] semop failed to
> getSharedLock: No space left on device
> Jan 27 23:54:00 inews nnrpd[8051]: [ID 745701 news.error] semop failed to
> release shared lock: Resource temporarily unavailable
> Jan 27 23:54:00 inews nnrpd[8051]: [ID 223153 news.error] semop failed to
> getSharedLock: No space left on device
> Jan 27 23:54:00 inews nnrpd[8051]: [ID 745701 news.error] semop failed to
> release shared lock: Resource temporarily unavailable
> Jan 27 23:54:00 inews nnrpd[8051]: [ID 223153 news.error] semop failed to
> getSharedLock: No space left on device
> Jan 27 23:54:00 inews nnrpd[8051]: [ID 745701 news.error] semop failed to
> release shared lock: Resource temporarily unavailable

You ran out of shared memory segments.  Solaris has a ridiculously low
default.  Somewhere around here, I have the magic to increase them....

Here we go.  In /etc/system:

set shmsys:shminfo_shmmax =3D 4294967295
set shmsys:shminfo_shmmin =3D 1
set shmsys:shminfo_shmmni =3D 100
set shmsys:shminfo_shmseg =3D 10
set semsys:seminfo_semmni =3D 100
set semsys:seminfo_semmsl =3D 1000
set semsys:seminfo_semmns =3D 2000
set semsys:seminfo_semopm =3D 100
set semsys:seminfo_semvmx =3D 32767

The particularly important ones are likely semmsl and semmns which control
the number of shared memory semaphores you can have.  The above is the
recommended configuration for Oracle servers.

--=20
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>

    Please send questions to the list rather than mailing me directly.
     <http://www.eyrie.org/~eagle/faqs/questions.html> explains why.