[MTT devel] Handling "Interrupted system call" with MTT

2007-10-16 Thread Ethan Mallove
On certain NFS servers, I run into the error message "Interrupted system call" when executing long running commands such as "make all". One solution I've been able to use is to setup an NFS mount point solely for the cluster I'm using, but this is not always an option. The below link advises to res

Re: [MTT devel] Handling "Interrupted system call" with MTT

2007-10-16 Thread Jeff Squyres
Ick! This is a long-known problem [apparently] with Sun's NFS, unfortunately. :-( I'd be ok with this if there is an eventual bail out of the loop -- the prospect of an infinite loop is a bit scary for me. On Oct 16, 2007, at 11:23 AM, Ethan Mallove wrote: On certain NFS servers, I ru

Re: [MTT devel] Handling "Interrupted system call" with MTT

2007-10-16 Thread Ethan Mallove
The bail is that "make" will eventually succeed or fail with something other than "interrupted system call". Do we need another condition? I do not know which system call is getting interrupted, but here's an interesting article on how different Unixes deal with connect() interruptions: http:/

Re: [MTT devel] Handling "Interrupted system call" with MTT

2007-10-16 Thread Jeff Squyres
On Oct 16, 2007, at 5:23 PM, Ethan Mallove wrote: The bail is that "make" will eventually succeed or fail with something other than "interrupted system call". Do we need another condition? I'm just worried that Sun's NFS will somehow get in a perpetual "interrupted system call" loop such tha

Re: [MTT devel] Handling "Interrupted system call" with MTT

2007-10-16 Thread Ethan Mallove
On Tue, Oct/16/2007 05:37:18PM, Jeff Squyres wrote: > On Oct 16, 2007, at 5:23 PM, Ethan Mallove wrote: > > > The bail is that "make" will eventually succeed or fail > > with something other than "interrupted system call". Do > > we need another condition? > > I'm just worried that Sun's NFS will