Hello Justin, On May 9, 7:35 pm, "Justin C. Walker" <[EMAIL PROTECTED]> wrote: > Hi, all, > > For the past few releases, I have had a number of odd build failures > while building SAGE[*]. Most of them turn out to be essentially > EAGAIN failures: fork() fails because I have too many processes > running. I bumped up the max processes per user on my system, to > 100. This worked for a while, but with 2.5, I ran into the fork > problem again. >
ulimit -a on OSX tells me that the hard coded limit for processes is 100 (per user), so this isn't really much. At http://www.macosxhints.com/article.php?story=200311151254441 you can find out how to increase the defaults to something more reasonable. > This means that it takes (up to) roughly 35-40 processes, running > simultaneously, to build SAGE. > Well, thank the autotools and your shell. Those two are real pigs resource wise, and make isn't frugal either. > This isn't a complaint, or a bug report :-}; the build process is > using all resources it can get. > I question the default choices for ulimit on MacOSX. It is not like a fork bomb would kill the box if maxproc were 512 instead of 100. It might be wise to add some blurb about these limitations the SAGE building instructions. Sooner or later somebody else will hit this problem. Cheers, Michael --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-forum URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~----------~----~----~----~------~----~------~--~---
