This bug was fixed in the package pam - 1.1.3-2ubuntu1
---------------
pam (1.1.3-2ubuntu1) oneiric; urgency=low
* Merge with Debian to get bug fix for unknown kernel rlimits. Remaining
changes:
- debian/libpam-modules.postinst: Add PATH to /etc/environment if it's
not present there or in /etc/security/pam_env.conf. (should send to
Debian).
- debian/libpam0g.postinst: only ask questions during update-manager when
there are non-default services running.
- Change Vcs-Bzr to point at the Ubuntu branch.
- debian/patches-applied/series: Ubuntu patches are as below ...
- debian/patches-applied/ubuntu-rlimit_nice_correction: Explicitly
initialise RLIMIT_NICE rather than relying on the kernel limits.
- debian/patches-applied/pam_motd-legal-notice: display the contents of
/etc/legal once, then set a flag in the user's homedir to prevent
showing it again.
- debian/update-motd.5, debian/libpam-modules.manpages: add a manpage
for update-motd, with some best practices and notes of explanation.
- debian/patches/update-motd-manpage-ref: add a reference in pam_motd(8)
to update-motd(5)
- debian/libpam0g.postinst: drop kdm from the list of services to
restart.
- debian/libpam0g.postinst: check if gdm is actually running before
trying to reload it.
- debian/local/common-session{,-noninteractive}: Enable pam_umask by
default, now that the umask setting is gone from /etc/profile.
- debian/local/pam-auth-update: Add the new md5sums for pam_umask addition.
- add debian/patches-applied/pam_umask_usergroups_from_login.defs.patch:
Deprecate pam_unix' explicit "usergroups" option and instead read it
from /etc/login.def's "USERGROUP_ENAB" option if umask is only defined
there. This restores compatibility with the pre-PAM behaviour of login.
(Closes: #583958)
* Dropped changes:
- debian/patches-applied/027_pam_limits_better_init_allow_explicit_root:
no need to bump the hard limit for number of file descriptors any more
since we read kernel limits directly now.
pam (1.1.3-2) unstable; urgency=low
[ Kees Cook ]
* debian/patches-applied/027_pam_limits_better_init_allow_explicit_root:
- only report about unknown kernel rlimits when "debug" is set
(Closes: 625226, LP: #794531).
[ Steve Langasek ]
* Build for multiarch. Closes: #463420.
* debian/patches-applied/027_pam_limits_better_init_allow_explicit_root:
don't reset the process niceness for root; since it's root, they can
still renice to a lower nice level if they need to and changing the
nice level by default is unexpected behavior. Closes: #594377.
-- Kees Cook <[email protected]> Thu, 18 Aug 2011 16:41:18 -0500
** Changed in: pam (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/794531
Title:
pam_limits: Unknown kernel rlimit 'Max realtime timeout' ignored
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/794531/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
