Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#3034 - pam-0.80-2 seems to break memlock limit

Attached to Project: Arch Linux
Opened by Ash (Thikasabrik) - Wednesday, 03 August 2005, 16:41 GMT
Last edited by arjan timmerman (blaasvis) - Wednesday, 02 November 2005, 10:22 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

With the 2.6.13-rc5 kernel (with working rtprio limit support) and the new PAM in testing, 'ulimit -l' gives 0 even through my limits.conf defines the memlock limit for the audio group, of which I am a member, as 350000. The limit also appears to be 0 for root! The rtprio limits work fine, but jack etc cannot lock memory any more...
This task depends upon

Closed by  arjan timmerman (blaasvis)
Sunday, 26 March 2006, 11:08 GMT
Reason for closing:  Fixed
Additional comments about closing:  works for me now.
Comment by Tobias Kieslich (tobias) - Sunday, 02 October 2005, 14:59 GMT
Just to let you know, I patched pam to get some of these settings at all. I really don't see a chance to get that working out of the box. So basically, this is an upstream issue. But I see what I can do.
Comment by Tobias Kieslich (tobias) - Sunday, 02 October 2005, 16:49 GMT
ok.
I just did a testbuild of 0.99.1.0 BETA (from here: https://www.redhat.com/archives/pam-list/2005-September/msg00024.html)
That solved the issue for me, but I dun feel like backporting upstream issues. If you like to build it yourself be aware that this snapshot has full autotools support, hence you have to tweak the PKGBUILD a bit...

Loading...