From: "Clif J. Smith" <plone@cjs226.com>
To: Ian Kent <raven@themaw.net>
Cc: autofs@linux.kernel.org
Subject: Re: Problem with NIS maps
Date: Wed, 01 Sep 2004 15:36:37 -0500 [thread overview]
Message-ID: <413632D5.3090301@cjs226.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0408312110390.2756@raven.themaw.net>
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
next prev parent reply other threads:[~2004-09-01 20:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 4:07 Problem with NIS maps Clif Smith
2004-08-31 13:13 ` Ian Kent
2004-09-01 12:54 ` Ryan Go
2004-09-01 15:03 ` Ian Kent
2004-09-01 20:36 ` Clif J. Smith [this message]
2004-09-04 4:06 ` raven
2004-08-31 15:43 ` Michael Blandford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=413632D5.3090301@cjs226.com \
--to=plone@cjs226.com \
--cc=autofs@linux.kernel.org \
--cc=raven@themaw.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.