Date: Thu, 16 Feb 2012 09:47:38 +0100 (CET) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= <Trond.Endrestol@fagskolen.gjovik.no> To: FreeBSD questions <freebsd-questions@freebsd.org> Subject: mlock(2) results in Resource temporarily unavailable on FreeBSD/amd64 9.0-STABLE Message-ID: <alpine.BSF.2.00.1202160924280.7134@mail.fig.ol.no>
next in thread | raw e-mail | index | archive | help
This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --2055831798-834928694-1329382058=:7134 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT I have a system running FreeBSD/amd64 9.0-STABLE as of Tue Jan 10 16:22:34 CET 2012. Every attempt by the root user to use the mlock(2) system call results in Resource temporarily unavailable (EAGAIN, 35). I'm using bash and ulimit -l says there's no restriction on the amount of locked memory: root@hostname:~>ulimit -l unlimited Is this typical for the amd64 arch? Is this documented somewhere? The mlock(2) system call works as expected on the i386 arch. GnuPG and other software would benefit from a useable mlock(2) on the amd64 arch. -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. dir. 61 14 54 39, | Office.....: +47 61 14 54 39, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ --2055831798-834928694-1329382058=:7134--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1202160924280.7134>