Open MPI logo

MTT Devel Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2007-10-16 16:59:29


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 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 restart the build on "Interrupted system call":
> I wrapped the make commands in a do-while to
> effect the build restarts. E.g.,
> do {
> $x = MTT::DoCommand::Cmd("make install")
> } while (!MTT::DoCommand::wsuccess($x->{exit_status}) and ($x->
> {result_stderr} =~ /interrupted system call/i));
> As long as make emits "interrupted system call" and fails,
> MTT will keep restarting make.
> I realize this is ugly, but is it acceptable?
> -Ethan
> _______________________________________________
> mtt-devel mailing list
> mtt-devel_at_[hidden]

Jeff Squyres
Cisco Systems