Eric Paris wrote:
> On Fri, 2008-04-11 at 12:10 -0400, Steve Dickson wrote:
>>> Does this mean the EACCES can/will again become fatal in mount.nfs like
>>> it used to be?
>> EACCES is still a non-fatal error as it was...
I guess I didn't look back far enough...
>
> "non-fatal error as it was"? Huh? Back in the days of binary mount
> data it was fatal. Try this on a new and old system.
Yes, I see...
> That may well have been your problem, but it doesn't change the fact the
> EACCES has been a fatal error in mount.nfs until just recently. Why was
> it changed? When is EACCES not fatal?
It appears the change came in with the text-based mount.nfs changes
commit 4ce9ddfb03de06e90fb4cf0eb5767cb0e3a98905
Author: Chuck Lever <chuck.lever@xxxxxxxxxx>
Date: Wed Oct 10 15:06:39 2007 -0400
text-based mount.nfs: sort between permanent and temporary errors
and I'm not sure why EACCES was deemed a non fatal error, but I'm
beginning to agree with you... EACCES probably should be fatal...
But thats something easily fixed in nfs-utils...
steved.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
