Re: [sage-devel] Re: Issue in parallel/use_fork.py

2012-04-21 Thread Stephen Montgomery-Smith
I figured it out. The problem was somewhere else completely - with python itself. I copied the patches from the FreeBSD port of python, and so far it is looking good. On 04/21/2012 05:20 PM, Volker Braun wrote: I guess the os.wait() throws an OSError with errno = EINTR because the SIGALARM

Re: [sage-devel] Re: Issue in parallel/use_fork.py

2012-04-21 Thread Volker Braun
I guess the os.wait() throws an OSError with errno = EINTR because the SIGALARM fires? If that is the case we should probably ignore it in use_fork.py On Saturday, April 21, 2012 3:36:44 PM UTC-4, Stephen Montgomery-Smith wrote: > > I did some research, and I found that you are completely c

Re: [sage-devel] Re: Issue in parallel/use_fork.py

2012-04-21 Thread Stephen Montgomery-Smith
I did some research, and I found that you are completely correct. I don't know why FreeBSD is misbehaving, because the os.wait command definitely triggers the OSError exception. signal.getsignal(SIGCHLD) shows that it is correctly set to signal.SIG_DFL. So I am mystified. Thank you for sett