From: Ian Kent <raven@themaw.net>
To: Filipe Brandenburger <lists.filbranden@idilia.com>
Cc: autofs@linux.kernel.org
Subject: Re: mount: mount point /home/user does not exist
Date: Tue, 07 Jul 2009 09:46:09 +0800 [thread overview]
Message-ID: <4A52A8E1.7030307@themaw.net> (raw)
In-Reply-To: <4A52038C.9090008@idilia.com>
Filipe Brandenburger wrote:
> Hi Ian,
>
> Ian Kent wrote:
>> Filipe Brandenburger wrote:
>>> Recently I had failures in some hosts when mounting home directories, in
>>> some cases more than one host at a time.
>>
>> This does sound a bit like a known problem.
>> A bunch of patches have gone into RHEL-4 U8 which resolved almost all
>> reported problems. You will need to log a bug or update to U8 to check.
>
> Thanks for your answer.
>
> Would upgrading autofs from 4.1.3-234 to 4.1.3-238 be enough, or do I
> need to upgrade to the latest kernel as well?
Above I was actually referring to the kernel, although I didn't make
that clear. The RHEL-4.8 kernel update fixed almost all reported kernel
related problems (there were a couple).
>
> Would using the "autofs5" package in RHEL4 be better in this sense? Do
> you know if that package is as stable as autofs 4 is in RHEL4?
That a trick question, right?
As the maintainer I will always recommend version 5.
The RHEL-4 autofs5 package is essentially the same as the RHEL-5 autofs
package except that it's a release behind, as updates are back ported.
The back porting of RHEL-5 updates will be somewhat more selective from
RHEL-4.9 onward.
Ian
next prev parent reply other threads:[~2009-07-07 1:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 22:26 mount: mount point /home/user does not exist Filipe Brandenburger
2009-07-03 4:38 ` Ian Kent
2009-07-06 14:00 ` Filipe Brandenburger
2009-07-07 1:46 ` Ian Kent [this message]
2009-07-09 22:03 ` Steve Linn
-- strict thread matches above, loose matches on Subject: below --
2009-07-02 21:36 Filipe Brandenburger
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=4A52A8E1.7030307@themaw.net \
--to=raven@themaw.net \
--cc=autofs@linux.kernel.org \
--cc=lists.filbranden@idilia.com \
/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.