9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Sam <sah@softcardsystems.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] DHCP weirdness?
Date: Thu, 24 Apr 2003 12:50:13 -0400	[thread overview]
Message-ID: <Pine.LNX.4.30.0304241236160.25655-100000@athena> (raw)
In-Reply-To: <5038f53ceb07079e037b1d023183e543@plan9.bell-labs.com>

Oddly enough, we're currently experiencing problems
that we only just discovered about 30 minutes ago.
It started with Brantley noting that our clients
were sending dhcp request messages on average about
one every two seconds.  He rebooted to see if it
would go away and now he can't get a terminal.
We replaced dhcpd on April 20 via replica/pull.
I guess we haven't rebooted our terminals since then.

We're using the ``proper'' plan9 setup with diskless
terminals and separate cpu/fs servers.

/sys/log/ipboot contains lines of the form:
	edsac Apr 24 12:42:37 not bootrequest

We replaced dhcpd with an older version, restarted it,
and all seems to be back to normal.  It is indeed
hard to use yesterday without singing. :)

Sam

On Thu, 24 Apr 2003, David Presotto wrote:

> I think rob saw this also.  Could you send me the ip/ipconfig line
> that you're using.  I changed it to fix arg processing and sysname
> defaulting (i.e. setting something useful in /net/ndb's sys= entry)
> but can't see what would have caused things to be completely ignored.
>
> All our systems run at boot.  Perhaps I broke something for systems
> running ipconfig out of termrc.
>



  reply	other threads:[~2003-04-24 16:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-24 16:09 Dan Cross
2003-04-24 16:24 ` David Presotto
2003-04-24 16:50   ` Sam [this message]
2003-04-24 16:53     ` David Presotto
2003-04-24 16:58     ` Charles Forsyth
2003-04-24 16:59     ` Russ Cox
2003-04-24 20:03   ` [9fans] ipconfig Sam
2003-04-24 20:56     ` David Presotto
2003-04-27 21:20       ` Russ Cox
2003-04-24 16:43 ` [9fans] DHCP weirdness? ron minnich

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=Pine.LNX.4.30.0304241236160.25655-100000@athena \
    --to=sah@softcardsystems.com \
    --cc=9fans@cse.psu.edu \
    /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).