Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 1 Jun 2010 02:45:38 +0100
From:      Bernardo Maciel <bernardo.maciel@gmail.com>
To:        Garrett Cooper <yanefbsd@gmail.com>
Cc:        ports <ports@freebsd.org>, python <python@freebsd.org>
Subject:   Re: FreeBSD Port: python26-2.6.5
Message-ID:  <AANLkTimlfATlYO4HQlL4fagZJv3twkKEnUOsI42oxDMI@mail.gmail.com>
In-Reply-To: <AANLkTiktYyfljF8o2kNeNL_i6TPigpT-ICD0sSjVRC1y@mail.gmail.com>
References:  <AANLkTimawN1I_Kwimyhb01nP3M4XR9ftMss1Da65Zun1@mail.gmail.com> <AANLkTiktYyfljF8o2kNeNL_i6TPigpT-ICD0sSjVRC1y@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 31, 2010 at 23:59, Garrett Cooper <yanefbsd@gmail.com> wrote:
> On Mon, May 31, 2010 at 9:49 AM, Bernardo Maciel
> <bernardo.maciel@gmail.com> wrote:
>> Hello,
>>
>>
>>
>> I recently ran into a problem when compiling python 2.6.5 under
>> FreeBSD 8.0-p2 . I searched around, asked in FreeBSD forums (
>> http://forums.freebsd.org/showthread.php?t=3D14268 ) and then e-mailed
>> the python-help mailing list. The problem isn't yet solved.
>>
>> My problem is that when I compile python 2.6.5, I get a "sem_init: No
>> space left on device" message when the script is building the _ssl
>> extension:
>
> ...
>
> =A0 =A0Increase the value of the kern.ipc.shmall sysctl because you have
> other applications eating up POSIX shmem in the background.
> HTH,
> -Garrett
>

Hello again,



Thank you for your reply. I increased the values of kern.ipc.shmall
and kern.ipc.shmmax but still no luck. I have 256MB RAM and 256MB of
swap space, so I searched around and chose 450MB for kern.ipc.shmmax,
which gives a value of 115200 for kern.ipc.shmall, since hw.pagesize
is 4096. The limit on kern.ipc.shmmax is RAM + swap, right?

Here is the kern.ipc sysctl:

------------------------------
FPserver# sysctl kern.ipc
kern.ipc.maxsockbuf: 262144
kern.ipc.sockbuf_waste_factor: 8
kern.ipc.somaxconn: 128
kern.ipc.max_linkhdr: 16
kern.ipc.max_protohdr: 60
kern.ipc.max_hdr: 76
kern.ipc.max_datalen: 124
kern.ipc.nmbjumbo16: 1096
kern.ipc.nmbjumbo9: 2192
kern.ipc.nmbjumbop: 4384
kern.ipc.nmbclusters: 8768
kern.ipc.piperesizeallowed: 1
kern.ipc.piperesizefail: 0
kern.ipc.pipeallocfail: 0
kern.ipc.pipefragretry: 0
kern.ipc.pipekva: 36864
kern.ipc.maxpipekva: 4169728
kern.ipc.msgseg: 2048
kern.ipc.msgssz: 8
kern.ipc.msgtql: 40
kern.ipc.msgmnb: 2048
kern.ipc.msgmni: 40
kern.ipc.msgmax: 16384
kern.ipc.semaem: 16384
kern.ipc.semvmx: 32767
kern.ipc.semusz: 136
kern.ipc.semume: 10
kern.ipc.semopm: 100
kern.ipc.semmsl: 60
kern.ipc.semmnu: 30
kern.ipc.semmns: 60
kern.ipc.semmni: 10
kern.ipc.semmap: 30
kern.ipc.shm_allow_removed: 0
kern.ipc.shm_use_phys: 0
kern.ipc.shmall: 115200
kern.ipc.shmseg: 128
kern.ipc.shmmni: 192
kern.ipc.shmmin: 1
kern.ipc.shmmax: 471859200
kern.ipc.maxsockets: 8768
kern.ipc.numopensockets: 11
kern.ipc.nsfbufsused: 0
kern.ipc.nsfbufspeak: 4
kern.ipc.nsfbufs: 2448
------------------------------

I still get the same message when the script is building the _ssl
extension. Can you help?



Best regards,

--=20
Bernardo



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimlfATlYO4HQlL4fagZJv3twkKEnUOsI42oxDMI>