From: Dylan <autofs@dylan.me.uk>
To: autofs mailing list <autofs@linux.kernel.org>
Subject: autofs4 and NIS
Date: Thu, 1 Jan 2004 01:59:12 +0000 [thread overview]
Message-ID: <200401010159.12640.autofs@dylan.me.uk> (raw)
Hello all,
I'm currently using autofs4 to mount nfs shares. The config files are
distributed via NIS, which overall is working without a hitch. I have
two related problems, however...
It is, obviously, necessary to restart the NIS server from time to time,
in order to take account of config changes (usually changes to user
accounts.) When I do this, the following occurs:
A: nfs shares which are unmounted become unavailable (cd-ing to the
directory results in a 'no such file or directory' error)
B: nfs shares which are mounted report stale file handles.
I can understand where problem A comes from - and I figure restarting
autofs would clear that, but it is not really practical to do on each
machine. But I'm not sure why B should happen...?
Dylan
--
Sweet moderation
Heart of this nation
Desert us not
We are between the wars
- Billy Bragg
next reply other threads:[~2004-01-01 1:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-01 1:59 Dylan [this message]
2004-01-01 4:13 ` autofs4 and NIS Ian Kent
2004-01-05 15:28 ` Todd Denniston
2004-01-05 16:21 ` 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=200401010159.12640.autofs@dylan.me.uk \
--to=autofs@dylan.me.uk \
--cc=autofs@linux.kernel.org \
/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.