From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] dhcpd and other CPU server fun.
Date: Mon, 21 Apr 2003 10:29:34 -0400 [thread overview]
Message-ID: <5da819aa6015a554830612e0ff392ecd@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0304210003180.15159-100000@maxroach.lanl.gov>
> Finally, sometimes when the CPU server comes up, it has the right IP
> address, and you can even cpu -h to it by its right hostname, but ndb/cs
> has set the wrong sysname in /dev/sysname. Again, this is pretty random.
> From one boot to the next it happens or it doesn't. Any idea why this
> would happen?
This fits with your other DHCP problems, which presotto answered.
If the rogue non-Plan 9 DHCP server answered, it might give out
the wrong sysname. I'm not sure how to turn off the VMware DHCP
server, but I bet it's in the documentation.
Ndb/cs sets the sysname using, in order:
an environment variable $sysname
the contents of /net/ndb (set during dhcp)
the current ip address, looked up in the network db
the current ether address, looked up in the network db
> The other thing I'm seeing is that the CPU server will get completely hung
> on the way up. The CPU server and auth server send packets out to each
> other, to no avail. Is this (I'm guessing) a VMWare thing, or is there
> something else going on? Anyone else seen this either with vmware or real
> hardware?
I've had no such problems with VMware, but it's been a while
since I did a boot over a virtual network.
Which network mode are you using?
Are they on the same virtual network?
Which packets are they sending to no avail?
Russ
prev parent reply other threads:[~2003-04-21 14:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-21 6:14 ron minnich
2003-04-21 6:34 ` nigel
2003-04-21 12:09 ` David Presotto
2003-04-21 16:02 ` ron minnich
2003-04-21 14:29 ` Russ Cox [this message]
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=5da819aa6015a554830612e0ff392ecd@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).