From: Ian Kent <raven@themaw.net>
To: Mike Marion <mmarion@qualcomm.com>
Cc: "autofs@linux.kernel.org" <autofs@linux.kernel.org>
Subject: Re: 5.0.5 non-expiring mounts
Date: Tue, 15 Feb 2011 20:28:53 +0800 [thread overview]
Message-ID: <1297772933.13007.28.camel@perseus> (raw)
In-Reply-To: <20110215052857.GV27735@sunapee.qualcomm.com>
On Mon, 2011-02-14 at 21:28 -0800, Mike Marion wrote:
> On Mon, Feb 14, 2011 at 07:37:01PM -0800, Ian Kent wrote:
>
> > That is kernel revision and autofs revision?
>
> 2.6.16.60-0.59.1 (Sles10 sp3 with an updated, but not bleeding edge, patch).
> autofs 5.0.5 with most of the patches up to a couple months ago. It's hard to
> get exacts because it's a PTF from Novell (we really pushed them to upgrade to
> 5.0.5) but it should be pretty much equal to the patch they just released for
> sle 11 sp1 that they're recommending as they default going forward.
That make it hard, as you know.
But I wouldn't mind spending a bit of time on it, if you can also.
Let's assume that it's a user space problem for now.
Could you post a debug log somewhere and the current sles patched source
somewhere. If you could spend a little time trying to compare the
patches in the sles package to the ones in the Rawhide autofs repo that
would be a big help too.
Ian
next prev parent reply other threads:[~2011-02-15 12:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 9:30 5.0.5 non-expiring mounts Philip Ong Jr.
2011-02-11 3:10 ` Ian Kent
2011-02-15 1:10 ` Mike Marion
2011-02-15 3:11 ` Ian Kent
2011-02-15 3:37 ` Ian Kent
2011-02-15 5:28 ` Mike Marion
2011-02-15 12:28 ` Ian Kent [this message]
2011-02-15 18:11 ` Leonardo Chiquitto
2011-02-16 7:08 ` Ian Kent
2011-02-16 12:18 ` Ian Kent
2011-02-23 20:22 ` Leonardo Chiquitto
2011-02-16 12:58 ` Leonardo Chiquitto
2011-03-04 20:10 ` Leonardo Chiquitto
2011-03-05 5:18 ` Ian Kent
2011-03-24 22:03 ` Leonardo Chiquitto
2011-03-28 3:17 ` Ian Kent
-- strict thread matches above, loose matches on Subject: below --
2011-02-17 1:08 Deke Clinger
2011-02-17 7:57 ` Ian Kent
2011-02-17 19:21 Deke Clinger
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=1297772933.13007.28.camel@perseus \
--to=raven@themaw.net \
--cc=autofs@linux.kernel.org \
--cc=mmarion@qualcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).