Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 5 Jun 2006 11:14:58 -0700
From:      David King <dking@ketralnis.com>
To:        freebsd-questions@freebsd.org
Cc:        Bill Moran <wmoran@collaborativefusion.com>
Subject:   Re: shmget: No space on device (sshit)
Message-ID:  <E9F563D9-7B1F-4887-872E-121DDA885C42@ketralnis.com>
In-Reply-To: <20060605125237.0dd0f77b.wmoran@collaborativefusion.com>
References:  <0CFDA5B7-6649-4891-BB66-31D9BCB83B38@ketralnis.com> <20060604085148.5f7c5287.wmoran@collaborativefusion.com> <A1281BE0-942C-454E-B4D2-FF6519033579@ketralnis.com> <20060604193932.1872024a.wmoran@collaborativefusion.com> <27CE73B8-B2DC-4EB5-A350-8259E7AFDD1A@ketralnis.com> <20060605125237.0dd0f77b.wmoran@collaborativefusion.com>

next in thread | previous in thread | raw e-mail | index | archive | help
>> I have all of the IPC-related sysctls listed below. I do see that
>> kern.ipc.shmmni is set to 192, and that kern.ipc.semmni is set to 10.
>> Are those the maximums? What does MNI mean in those names? Is there a
>> man page or recommended document that describes what these mean in
>> detail?
> ipcs -M or /usr/src/sys/conf/NOTES
> I believe the "mni" portion is "maximum number of identifiers".

ipcs -M shows:
shminfo:
         shmmax: 134217728       (max shared memory segment size)
         shmmin:       1 (min shared memory segment size)
         shmmni:     192 (max number of shared memory identifiers)
         shmseg:     128 (max shared memory segments per process)
         shmall:    8192 (max amount of shared memory in pages)

So yes, it had definitely reached its max.

So I used ipcrm to remove all of the shared memory segments, and the  
problem seems to have cleared up for now. A few rounds of simulating  
failed logins to sshit shows that it does allocate shared memory  
segments, and every time it adds an IP address it seems to allocate a  
new shared memory segment instead of finding the old one.

But from here it looks like an issue to take up with the developer,  
since it seems to be a bug. Thanks Bill for your help!



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E9F563D9-7B1F-4887-872E-121DDA885C42>