From: Ian Kent <raven@themaw.net>
To: "Breitman, Jason" <Jason.Breitman@blackrock.com>
Cc: autofs@linux.kernel.org
Subject: Re: automount restart required
Date: Thu, 05 Nov 2009 09:48:32 +0800 [thread overview]
Message-ID: <4AF22EF0.6060501@themaw.net> (raw)
In-Reply-To: <5FAC3462B446C244A45ED5303B61491111920A20@NYCPEXV005.na.blkint.com>
Breitman, Jason wrote:
> Am I reading the version number wrong or is there a different numbering
> scheme inside of RHEL then in Fedora?
Don't be difficult.
All the important fixes are included in the RHEL-5 revision.
In fact, a lot of the time the fixes in the upstream package come from
work on RHEL reported bugs. Admittedly, it can be a while before they
make it into a RHEL release due to the process but the RHEL-5 version
you are using is very close to the Fedora version.
>
> http://mirrors.kernel.org/fedora/releases/11/Everything/i386/os/Packages
> /autofs-5.0.4-24.i586.rpm
>
> I will work on submitting a bug.
>
> All I meant by issues is that I would rather deal with losing my
> official Redhat Support by using a Redhat unapproved, yet more stable,
> version of autofs then continue to use the Redhat approved autofs
> package and have automount issues. Hopefully that makes sense.
>
>
> Jason Breitman
> jason.breitman@blackrock.com
>
> -----Original Message-----
> From: Ian Kent [mailto:raven@themaw.net]
> Sent: Tuesday, November 03, 2009 8:56 PM
> To: Breitman, Jason
> Cc: autofs@linux.kernel.org
> Subject: Re: [autofs] automount restart required
>
> Breitman, Jason wrote:
>> Operating System: RHEL 5.3 (32 bit)
>>
>> kernel package: kernel-2.6.18-128.el5
>>
>> autofs package: autofs-5.0.1-0.rc2.131.el5_4.1
>>
>> nfs-utils package: nfs-utils-1.0.9-40.el5
>>
>> Map Type: Direct Map stored in NIS
>>
>> Issue:
>> Users and applications will not be able to get into one of the
>> directories in the direct map.
>> The system reports no such file or directory.
>> I can get to the mount point, but not any further.
>>
>> * I can not reproduce the issue on demand.
>> ** The issue does happen on multiple hosts with the same build.
>>
>> Resolution:
>> /etc/init.d/autofs restart
>>
>> Question:
>> I noticed much later versions of autofs on Fedora. (autofs-5.0.4-XXX)
>> I also read the changelog and there are many fixes that might be
>> considered a solution to my problem.
>
> I doubt it.
> The RHEL version you have is actually quite close to the Fedora version.
>
>> Bottom line is what is the most stable package of autofs that I should
>> be using on my RHEL 5.3 Systems.
>
> The version you have is the latest RHEL version.
> I'm not aware of the problem you describe so log a bug and include your
> maps, a debug log showing the problem and any other information like how
> often it happens.
>
>> I understand that RHEL support may be affected, but would be willing
> to
>> deal with those issues.
>
> So now there is more than one issue, what are the other issues?
>
>> Thanks.
>>
>> Jason Breitman
>> jason.breitman@blackrock.com
>>
>> THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE
> PRIVILEGED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM
> DISCLOSURE. If the reader of this message is not the intended recipient,
> you are hereby notified that any dissemination, distribution, copying or
> use of this message and any attachment is strictly prohibited. If you
> have received this message in error, please notify us immediately by
> replying to the message and permanently delete it from your computer and
> destroy any printout thereof.
>> _______________________________________________
>> autofs mailing list
>> autofs@linux.kernel.org
>> http://linux.kernel.org/mailman/listinfo/autofs
>
>
> THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof.
>
> _______________________________________________
> autofs mailing list
> autofs@linux.kernel.org
> http://linux.kernel.org/mailman/listinfo/autofs
next prev parent reply other threads:[~2009-11-05 1:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 16:53 automount restart required Breitman, Jason
2009-11-04 1:55 ` Ian Kent
2009-11-04 21:43 ` Breitman, Jason
2009-11-05 1:48 ` Ian Kent [this message]
2009-11-05 1:58 ` Ian Kent
2009-11-06 0:55 ` Breitman, Jason
2009-11-06 1:49 ` Ian Kent
2009-11-10 15:56 ` Breitman, Jason
2009-11-16 3:13 ` Breitman, Jason
2009-11-16 8:40 ` 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=4AF22EF0.6060501@themaw.net \
--to=raven@themaw.net \
--cc=Jason.Breitman@blackrock.com \
--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.