mlock(2) results in Resource temporarily unavailable on
FreeBSD/amd64 9.0-STABLE
Trond Endrestøl
Trond.Endrestol at fagskolen.gjovik.no
Thu Feb 16 08:47:50 UTC 2012
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 at 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. |
+-------------------------------+------------------------------------+
More information about the freebsd-questions
mailing list