[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug #38420] $(realpath ...) doesn't recover from signals

From: Brian Vandenberg
Subject: Re: [bug #38420] $(realpath ...) doesn't recover from signals
Date: Wed, 27 Feb 2013 12:47:54 -0700

On Wed, Feb 27, 2013 at 11:36 AM, Philip Guenther <address@hidden> wrote:
> On Wed, Feb 27, 2013 at 9:44 AM, Brian Vandenberg
> <address@hidden> wrote:
>> Follow-up Comment #3, bug #38420 (project make):
>>   You're spot on.  It is Solaris / NFS 3.
>>   In the interim I'm using a build with the fix I suggested.
>>   Do you know of a workaround for this that wouldn't require deploying a
>> modified version of make?
> Doesn't this problem only occur if the NFS mount has the 'intr' flag?
> (The intr flag basically means "violate the historical UNIX behavior
> because I don't trust my NFS server to recover quickly and reliably
> and need a way to bail out, regardless of the consequences"...)
> Philip Guenther

hm ... The documentation for NFS recommends configuring with 'hard'
and 'intr' so it'll allow signals to interrupt (causing some platforms
to set errno = EINTR and fail) ... and it looks like 'hard' is the
default.  The mount point isn't configured explicitly with 'hard', but
if the documentation I'm reading is accurate then it should be set to
'hard' by default.

What it doesn't make clear is, if it's configured with 'nointr' will
that just cause the system function to block?  That seems the most

Anyway, thanks for that; it gives me something else to pursue.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]