From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] odd problem with auth (?)
Date: Tue, 12 Jul 2011 14:16:01 -0400 [thread overview]
Message-ID: <a99a1329b80e3e6bbbf12278101f0603@ladd.quanstro.net> (raw)
In-Reply-To: <CAL4LZyi3V0jf3u1HAEJPD0yxss7mYkD_AvYoMA2z5sZb0L6+Yw@mail.gmail.c>
> My /lib/ndb/local contains these lines (gozer gets its IP from a
> different DHCP server):
>
> auth=gozer authdom=mydom
>
> sys=gozer dom=gozer.mydom
>
> sys=zuul dom=zuul.mydom
> bootf=/386/9pxeload
> ip=10.1.18.192 ether=<whatever>
>
> Here are some commands I've tried, and the results I've seen:
>
> term% cpu -h gozer
> cpu: can't dial: gozer: port unreachable
so where would your term lookup the ip address of gozer?
- erik
next parent reply other threads:[~2011-07-12 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAL4LZyi3V0jf3u1HAEJPD0yxss7mYkD_AvYoMA2z5sZb0L6+Yw@mail.gmail.c>
2011-07-12 18:16 ` erik quanstrom [this message]
2011-07-12 18:36 ` John Floren
2011-07-12 19:24 ` John Floren
2011-07-12 18:11 John Floren
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=a99a1329b80e3e6bbbf12278101f0603@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).