http://sourceforge.net/bugs/?func=detailbug&bug_id=119554&group_id=6663 Thanks Andrew "Adam J. Richter" wrote: > > Linux-PAM-0.72/modules/pam_limits/pam_limits.c initializes > an array called "limits" one element at a time based on each resouce > type that it knows about, using getrlimit. However, it sets the > resources values (using setrlimit) by just iterating from 0 to > RLIMIT_NLIMITS-1. Recent Linux 2.4.0 kernels have added at least > one new resource id (RLIMIT_LOCKS), which ends up being set to > zero because the extra element in limits[] was not initialized. > This means that processes has no right to lock any files, so > many things break, such as simply sending email. > > I have attached a fix below, which also makes the code slightly > smaller.
