public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: J Sloan <joe@tmsusa.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: recent rwhod woes
Date: Sat, 19 Apr 2003 12:06:51 -0700	[thread overview]
Message-ID: <3EA19E4B.7000201@tmsusa.com> (raw)

Hi, just a reminder that rwhod is broken in recent 2.5.67-xx kernels.

I had earlier reported it incorrectly, saying I first saw the problem
in 2.5.67-mm3, but going back to verify, I see that 2.5.67-mm1 is OK
while 2.5.67-mm2 through -mm4 are broken.

I noticed that rwhod is OK in 2.5.67 + linux patchset 1.1177, but
adding the sk-allocation patch (from -mm2) breaks rwhod.

The symptom here is that running the "ruptime" command on an -mm2
box shows all hosts down - however the other hosts on the subnet are
getting the rwho broadcasts from the -mm2 box, but the -mm2 box is
unable to process rwho broadcasts, including it's own -

I'd hoped I could narrow it down to that patch, but backing out that
single patch does not fix -mm2 through -mm4, so it appears that while
the one patch will break rwhod, there are apparently other changes
that also break rwhod independently of the sk-allocation patch, and
the answer is more involved than I'd hoped.

I've been hammered at work lately so time is limited, but I did want
to raise the rwhod issue again - if I get some time I'll check the
plain -bk tree, or if someone has any ideas I'll be happy to act as
a patch & test monkey in my spare time.

Best Regards,

Joe



                 reply	other threads:[~2003-04-19 18:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3EA19E4B.7000201@tmsusa.com \
    --to=joe@tmsusa.com \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox