From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] dist updates from sources.cs.bell-labs.com
Date: Sat, 26 Oct 2002 14:20:19 -0400 [thread overview]
Message-ID: <b8c5827138297fbde2f4f60fcaa07c2d@plan9.bell-labs.com> (raw)
you're not even trying to authenticate:
there's nothing in our logs.
after you run a failed attempt at pulling,
try running auth/debug to see what it
thinks about your auth setup. (the failed
pull attempt will store the key you used,
which is important.)
everything you posted looks reasonable to me.
if you only just edited /lib/ndb/local
(and haven't rebooted since then)
you'll have to
echo -n refresh >/net/cs
to get it to reread the file.
next reply other threads:[~2002-10-26 18:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-26 18:20 Russ Cox [this message]
2002-10-28 20:01 ` Chris Silva
-- strict thread matches above, loose matches on Subject: below --
2002-10-29 1:57 YAMANASHI Takeshi
2002-10-28 23:21 Russ Cox
2002-10-29 1:48 ` Chris Silva
2002-10-28 21:19 Russ Cox
2002-10-28 22:21 ` Chris Silva
2002-10-26 16:21 Chris Silva
2002-10-23 20:12 Russ Cox
2002-10-23 13:50 Russ Cox
2002-10-23 16:43 ` Chris Silva
2002-10-23 18:43 ` andrey mirtchovski
2002-10-23 18:52 ` Dan Cross
2002-10-23 19:01 ` andrey mirtchovski
2002-10-23 23:14 ` Chris Silva
2002-10-23 9:56 Chris Silva
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=b8c5827138297fbde2f4f60fcaa07c2d@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).