From: Greg Wooledge <wooledg@eeg.ccf.org>
To: autofs mailing list <autofs@linux.kernel.org>
Subject: Re: [RFC] Towards a Modern Autofs
Date: Wed, 7 Jan 2004 09:05:25 -0500 [thread overview]
Message-ID: <20040107140525.GE20597@eeg.ccf.org> (raw)
In-Reply-To: <6AB920CC10586340BE1674976E0A991D0C6BE4@slexch2.sugarland.unocal.com>
On Tue, Jan 06, 2004 at 04:28:59PM -0600, Ogden, Aaron A. wrote:
> On those occasions where the autofs daemon gets confused
> (loses track of mountpoints, gets corruption in its internal
> representation of NIS maps, etc.) we could shut down the autofs daemon,
> kill any remaining processes, and restart it from scratch. In most
> cases restarting the daemon fixes the problem. It's worth noting that I
> have seen this happen on Solaris 2.6 as well but it is extremely rare.
I do it on HP-UX 10.20 all the time. Lots of stale NFS handles, or
something just isn't working right? Stop and restart the automount
daemons (/sbin/init.d/nfs.client), and that usually fixes it. The one
or two times I made the mistake of trying that on Linux, I had to reboot
the box to get it to work again.
next prev parent reply other threads:[~2004-01-07 14:05 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-06 22:28 [RFC] Towards a Modern Autofs Ogden, Aaron A.
2004-01-06 22:28 ` [autofs] " Ogden, Aaron A.
2004-01-06 22:41 ` Mike Fedyk
2004-01-06 22:47 ` Tim Hockin
2004-01-06 22:53 ` Paul Raines
2004-01-06 22:53 ` [autofs] " Paul Raines
2004-01-07 14:05 ` Greg Wooledge [this message]
2004-01-07 23:14 ` Jim Carter
2004-01-07 23:14 ` [autofs] " Jim Carter
2004-01-07 23:32 ` H. Peter Anvin
2004-01-07 23:32 ` [autofs] " H. Peter Anvin
2004-01-08 12:52 ` Ian Kent
2004-01-08 12:52 ` Ian Kent
2004-01-08 18:31 ` viro
2004-01-09 18:43 ` Ian Kent
2004-01-09 18:43 ` [autofs] " Ian Kent
2004-01-09 19:41 ` Mike Waychison
2004-01-09 19:41 ` [autofs] " Mike Waychison
2004-01-09 19:57 ` H. Peter Anvin
2004-01-09 19:57 ` [autofs] " H. Peter Anvin
2004-01-09 21:31 ` Mike Waychison
2004-01-09 21:31 ` [autofs] " Mike Waychison
2004-01-09 21:36 ` H. Peter Anvin
2004-01-09 21:36 ` [autofs] " H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2004-01-12 22:50 Tim Hockin
2004-01-13 1:30 ` Ian Kent
2004-01-12 16:58 [autofs] " Mike Waychison
2004-01-13 1:54 ` Ian Kent
2004-01-13 19:01 ` Mike Waychison
2004-01-10 5:43 [autofs] " Ian Kent
2004-01-12 13:07 ` Mike Waychison
2004-01-12 16:01 ` raven
2004-01-13 18:46 ` Mike Waychison
2004-01-08 15:39 [autofs] " Mike Waychison
2004-01-09 18:20 ` Ian Kent
2004-01-09 20:06 ` Mike Waychison
2004-01-09 20:51 ` Jim Carter
2004-01-06 23:34 Ogden, Aaron A.
2004-01-06 23:26 Ogden, Aaron A.
2004-01-06 19:55 Mike Waychison
2004-01-06 19:55 ` Mike Waychison
2004-01-06 21:01 ` H. Peter Anvin
2004-01-06 21:44 ` Mike Waychison
2004-01-06 21:50 ` Tim Hockin
2004-01-06 22:06 ` H. Peter Anvin
[not found] ` <20040106221502.GA7398@hockin.org>
2004-01-06 22:20 ` H. Peter Anvin
2004-01-07 16:19 ` Mike Waychison
2004-01-07 21:14 ` Jim Carter
2004-01-07 22:55 ` Mike Waychison
2004-01-08 12:00 ` Ian Kent
2004-01-08 17:34 ` [autofs] " H. Peter Anvin
2004-01-08 23:42 ` Michael Clark
2004-01-09 20:28 ` Mike Waychison
2004-01-09 20:54 ` H. Peter Anvin
2004-01-09 21:43 ` Mike Waychison
2004-01-09 18:32 ` Ian Kent
2004-01-09 20:52 ` Mike Waychison
2004-01-08 0:48 ` Ian Kent
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=20040107140525.GE20597@eeg.ccf.org \
--to=wooledg@eeg.ccf.org \
--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.