Did the initially proposed workaround help anyone?

Workaround: explicitly specifying the port in the mount map disables
> autofs' portmapper attempts:
> -port=2049,-fstype=nfs4,sec=krb5,actimeo=5,timeo=60


It looks like this is currently scheduled for the RHEL 6.4 GA (~Jan/Feb
2013).



On Mon, Sep 17, 2012 at 9:26 AM, Pat Riehecky <[log in to unmask]> wrote:

> On 09/13/2012 05:27 AM, Jonathan Underwood wrote:
>
>> Hi,
>>
>> Autofs in SL 6.3 has some problems with mounting NFSv4 filesystems. These
>> problems are also present in the TUVs packages, so this is not specific to
>> SL. The details are in this bug report:
>>
>> https://bugzilla.redhat.com/**show_bug.cgi?id=834641<https://bugzilla.redhat.com/show_bug.cgi?id=834641>
>>
>> There are some updated packages here:
>>
>> http://people.redhat.com/~**ikent/autofs-5.0.5-55.el6<http://people.redhat.com/~ikent/autofs-5.0.5-55.el6>
>>
>> which it seems like are probably not going to make it out until TUV 6.4
>> release.
>>
>> I wonder if SL should consider making these updates available somewhere
>> (eg. the rolling tree or fastbugs or somesuch) - I realize this flies in
>> the face of the principle of sticking as close as possible to TUV. Anyway,
>> just wanted to raise awareness of the issue if nothing else.
>>
>> Cheers,
>> Jonathan.
>>
>
> Hi Jonathan,
>
> We don't typically package pre-release rpms from upstream.  I appreciate
> the notification on the problem, as I'm sure others do as well.
>  Information is always good.
>
> I've added myself to the CC list on the bug to keep an eye on this
> package's progress.
>
> Pat
>
> --
> Pat Riehecky
> Scientific Linux Developer
>



-- 
Thanks,

Jamie Duncan