From: Ian Kent <raven@themaw.net>
To: Steve Thompson <smt@vgersoft.com>
Cc: autofs@linux.kernel.org
Subject: Re: Wrong network
Date: Tue, 15 Feb 2011 21:03:08 +0800 [thread overview]
Message-ID: <1297774988.13007.43.camel@perseus> (raw)
In-Reply-To: <alpine.LRH.0.9999.1102150729250.16053@helios.vgersoft.com>
On Tue, 2011-02-15 at 07:40 -0500, Steve Thompson wrote:
> On Tue, 15 Feb 2011, Ian Kent wrote:
>
> > Fair call, but it comes over as though you don't want to contribute at
> > all, which isn't good.
>
> That's not the impression I meant to give at all. I _am_ building some new
> test machines (about ten of them), and I _will_ do some testing. My test
> machines will all be 32-bit, though, as there is no spare 64-bit hardware.
> I just can't go testing on a production network; what with this and the
> hang problem I described in a separate post, I'm close enough to being
> lynched as it is. I have written my own applications of a similar level of
> complexity to autofs, and I certainly appreciate that it's not easy, and I
> definitely appreciate the job that you're doing.
We're good then.
I appreciate you are in a difficult spot, but spare a thought for the
pressures I may have that tent to make me a bit short from time to
time, ;)
As far as the hang you have seen, I don't know why that's happening, the
patches were added between el5_5.4 and el5_5.6 have been around for
quite a while, upstream and in Fedora and tested by more than one
customer, so I didn't expect to hear of a problem. Like I said, send me
a gdb backtrace so that I can see where it's happening.
Just to confirm, this is autofs-5.0.1-0.rc2.143.el5_5.6, and what kernel
revision, I guess the same as RHEL-5.5, which should be fine.
I can post the previous RedHat package to people.redhat.com so you can
revert back while we work on this, if that will kelp.
Ian
next prev parent reply other threads:[~2011-02-15 13:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-12 14:29 Wrong network Steve Thompson
2011-02-12 15:38 ` Frank Thommen
2011-02-12 19:28 ` Steve Thompson
2011-02-12 20:21 ` Steve Thompson
2011-02-14 2:06 ` Ian Kent
2011-02-14 19:22 ` Steve Thompson
2011-02-15 3:06 ` Ian Kent
2011-02-15 12:04 ` Steve Thompson
2011-02-15 12:15 ` Ian Kent
2011-02-15 12:40 ` Steve Thompson
2011-02-15 13:03 ` Ian Kent [this message]
2011-02-16 22:00 ` Steve Thompson
2011-02-17 1:58 ` 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=1297774988.13007.43.camel@perseus \
--to=raven@themaw.net \
--cc=autofs@linux.kernel.org \
--cc=smt@vgersoft.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.