| To: | Derek Glidden <dglidden@xxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Anyone know what this error means? |
| From: | Andi Kleen <ak@xxxxxxx> |
| Date: | Wed, 9 Jan 2002 19:09:23 +0100 |
| Cc: | Nathan Scott <nathans@xxxxxxx>, Adam McKenna <adam-dated-1010968404.3db79f@xxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <1010597638.18156.2.camel@two> |
| References: | <20020109003323.GW4511@xxxxxxxxxxxx> <20020109115309.A3063@xxxxxxxxxxxxxxxxxxxxxxxx> <1010597638.18156.2.camel@two> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Mutt/1.3.22.1i |
On Wed, Jan 09, 2002 at 12:33:57PM -0500, Derek Glidden wrote: > It apparently *is* a kernel bug, with the basic problem being that for > some reason the kernel isn't recognizing ulimits if you 'su' to the root > user. (Although in my experience it will also pop up if you "ssh" The problem is a broken pam_limits. It has nothing to do with the kernel. root, su and sudo have different pam setups. Likely all problems will go away if you comment out pam_limits from all files in /etc/pam.d/* There were historically some problems with quotas because the value meaning unlimited quota was once different in glibc and kernel, which caused and still causes endless confusion -Andi |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Anyone know what this error means?, Andi Kleen |
|---|---|
| Next by Date: | Re: Anyone know what this error means?, Austin Gonyou |
| Previous by Thread: | Re: Anyone know what this error means?, Derek Glidden |
| Next by Thread: | Re: Anyone know what this error means?, Austin Gonyou |
| Indexes: | [Date] [Thread] [Top] [All Lists] |