Problem with NIS maps

Problem with NIS maps

[Clif Smith]

I'm in a large heterogeneous environment located across multiple 
locations.  I use NIS maps such as:
/home -rw austin:/export/home boston:/export/home phoenix:/export/home

with the following in /etc/auto.master:
/nis      yp      auto_indirect_nis

With AIX and Solaris, automounter chooses the server with the fewest
hops to determine which server to mount from.  Unfortunately, it appears
Suse's 8.1 implementation of automounter (v3.1.7-556) seems to choose 
the first listed.

Has anyone run into this before?

Thanks, Clif

Re: Problem with NIS maps

[Ian Kent]

On Mon, 30 Aug 2004, Clif Smith wrote:

> I'm in a large heterogeneous environment located across multiple 
> locations.  I use NIS maps such as:
> /home -rw austin:/export/home boston:/export/home phoenix:/export/home
> 
> with the following in /etc/auto.master:
> /nis      yp      auto_indirect_nis
> 
> With AIX and Solaris, automounter chooses the server with the fewest
> hops to determine which server to mount from.  Unfortunately, it appears
> Suse's 8.1 implementation of automounter (v3.1.7-556) seems to choose 
> the first listed.

Sorry, SuSE have chosen not to update to autofs v4.

The most recent version handles this.

You may wish to try building the SRPM from one of the FC distributions.

Ian

Re: Problem with NIS maps

[Ryan Go]

Hello,

We don't use the replicated stuff so I am not sure if it works with SuSE.
But 8.1 has autofs v4 (not the latest one though), you might wanna check
it out.

HTH,
	<< ryan

On Tue, 31 Aug 2004, Ian Kent wrote:

> On Mon, 30 Aug 2004, Clif Smith wrote:
>
> > I'm in a large heterogeneous environment located across multiple
> > locations.  I use NIS maps such as:
> > /home -rw austin:/export/home boston:/export/home phoenix:/export/home
> >
> > with the following in /etc/auto.master:
> > /nis      yp      auto_indirect_nis
> >
> > With AIX and Solaris, automounter chooses the server with the fewest
> > hops to determine which server to mount from.  Unfortunately, it appears
> > Suse's 8.1 implementation of automounter (v3.1.7-556) seems to choose
> > the first listed.
>
> Sorry, SuSE have chosen not to update to autofs v4.
>
> The most recent version handles this.
>
> You may wish to try building the SRPM from one of the FC distributions.
>
> Ian
>
> _______________________________________________
> autofs mailing list
> autofs@linux.kernel.org
> http://linux.kernel.org/mailman/listinfo/autofs
>

Re: Problem with NIS maps

[Ian Kent]

On Wed, 1 Sep 2004, Ryan Go wrote:

> Hello,
> 
> We don't use the replicated stuff so I am not sure if it works with SuSE.
> But 8.1 has autofs v4 (not the latest one though), you might wanna check
> it out.

SuSE 9.1 includes 4.0.0, my release of the largely unchanged 4.0.0pre10. 
I don't know what patches they've applied but still quite old.

> 
> HTH,
> 	<< ryan
> 
> On Tue, 31 Aug 2004, Ian Kent wrote:
> 
> > On Mon, 30 Aug 2004, Clif Smith wrote:
> >
> > > I'm in a large heterogeneous environment located across multiple
> > > locations.  I use NIS maps such as:
> > > /home -rw austin:/export/home boston:/export/home phoenix:/export/home
> > >
> > > with the following in /etc/auto.master:
> > > /nis      yp      auto_indirect_nis
> > >
> > > With AIX and Solaris, automounter chooses the server with the fewest
> > > hops to determine which server to mount from.  Unfortunately, it appears
> > > Suse's 8.1 implementation of automounter (v3.1.7-556) seems to choose
> > > the first listed.
> >
> > Sorry, SuSE have chosen not to update to autofs v4.
> >
> > The most recent version handles this.
> >
> > You may wish to try building the SRPM from one of the FC distributions.
> >
> > Ian
> >
> > _______________________________________________
> > autofs mailing list
> > autofs@linux.kernel.org
> > http://linux.kernel.org/mailman/listinfo/autofs
> >
> 

Re: Problem with NIS maps

[Clif J. Smith]

Ian Kent wrote:

>On Mon, 30 Aug 2004, Clif Smith wrote:
>
>  
>
>>I'm in a large heterogeneous environment located across multiple 
>>locations.  I use NIS maps such as:
>>/home -rw austin:/export/home boston:/export/home phoenix:/export/home
>>
>>with the following in /etc/auto.master:
>>/nis      yp      auto_indirect_nis
>>
>>With AIX and Solaris, automounter chooses the server with the fewest
>>hops to determine which server to mount from.  Unfortunately, it appears
>>Suse's 8.1 implementation of automounter (v3.1.7-556) seems to choose 
>>the first listed.
>>    
>>
>
>Sorry, SuSE have chosen not to update to autofs v4.
>
>The most recent version handles this.
>
>You may wish to try building the SRPM from one of the FC distributions.
>
>Ian
>  
>
I ASSuMEd compiling it from source (4.1.3) would be even "cleaner", but 
when I see that /etc/init.d/autofs has:
if [ -f /etc/debian_version ]; then
    system=debian
elif [ -f /etc/redhat-release ]; then
    system=redhat
else
    echo "$0: Unknown system, please port and contact 
autofs@linux.kernel.org" 1>&2
    exit 1
fi

Why is the source so restrictive?

Moving on to the FC SRPM.

cjs

Re: Problem with NIS maps

[raven]

On Wed, 1 Sep 2004, Clif J. Smith wrote:

> Ian Kent wrote:
> 
> >On Mon, 30 Aug 2004, Clif Smith wrote:
> >
> >  
> >
> >>I'm in a large heterogeneous environment located across multiple 
> >>locations.  I use NIS maps such as:
> >>/home -rw austin:/export/home boston:/export/home phoenix:/export/home
> >>
> >>with the following in /etc/auto.master:
> >>/nis      yp      auto_indirect_nis
> >>
> >>With AIX and Solaris, automounter chooses the server with the fewest
> >>hops to determine which server to mount from.  Unfortunately, it appears
> >>Suse's 8.1 implementation of automounter (v3.1.7-556) seems to choose 
> >>the first listed.
> >>    
> >>
> >
> >Sorry, SuSE have chosen not to update to autofs v4.
> >
> >The most recent version handles this.
> >
> >You may wish to try building the SRPM from one of the FC distributions.
> >
> >Ian
> >  
> >
> I ASSuMEd compiling it from source (4.1.3) would be even "cleaner", but 
> when I see that /etc/init.d/autofs has:
> if [ -f /etc/debian_version ]; then
>     system=debian
> elif [ -f /etc/redhat-release ]; then
>     system=redhat
> else
>     echo "$0: Unknown system, please port and contact 
> autofs@linux.kernel.org" 1>&2
>     exit 1
> fi
> 
> Why is the source so restrictive?
> 
> Moving on to the FC SRPM.
> 

Yes, that's a good point.

This is one of the issues that should be addressed when the master map 
parsing is taken into the daemon. It's pretty much the highest priority 
task atm.

Ian

Re: Problem with NIS maps

[Michael Blandford]

Clif Smith wrote:

> I'm in a large heterogeneous environment located across multiple 
> locations.  I use NIS maps such as:
> /home -rw austin:/export/home boston:/export/home phoenix:/export/home
>
> with the following in /etc/auto.master:
> /nis      yp      auto_indirect_nis
>
> With AIX and Solaris, automounter chooses the server with the fewest
> hops to determine which server to mount from.  Unfortunately, it appears
> Suse's 8.1 implementation of automounter (v3.1.7-556) seems to choose 
> the first listed.
>
> Has anyone run into this before?


Yes, it is called replicated server.

It is supported in the autofs-4.1.x family.  You should upgrade.

Disclaimer: The content of this message is my personal opinion only and 
although I am an employee of Intel, the statements I make here in no way 
represent Intel's position on the issue, nor am I authorized to speak on 
behalf of Intel on this matter.

Michael