On Fri, May 13, 2005 at 03:55:39PM -0400, Daniel Jacobowitz wrote: > On Fri, May 13, 2005 at 08:32:53PM +0100, Matthew Wilcox wrote: > > Well, how can we fix this for sarge then? Either we need to change glibc > > or the kernel, both of which are extremely deeply frozen. I'd rather > > fix this by reverting to our previous behaviour of assuming 8MB stacks > > for threads than change the kernel's behaviour to limit stacks to 8MB > > by default. That would seem to risk breaking much more stuff. > > I'm not following. Are you saying that the changed ulimit is the > result of a kernel change? That seems very strange, since sarti has a > 134 day uptime and did not have this problem building glibc a month > ago for -21.
No, the kernel's had a 1GB ulimit for years. Something must've changed in glibc. > If you want to change glibc at this point, discuss with Carlos; I can't > take care of it. Just getting -22 built has taken most of my free time > for this week. Carlos? This seems like your fault, how do *you* want to fix it? ;-) -- "Next the statesmen will invent cheap lies, putting the blame upon the nation that is attacked, and every man will be glad of those conscience-soothing falsities, and will diligently study them, and refuse to examine any refutations of them; and thus he will by and by convince himself that the war is just, and will thank God for the better sleep he enjoys after this process of grotesque self-deception." -- Mark Twain -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
