From: James Cook <james.cook@utoronto.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] sources down?
Date: Wed, 29 Nov 2006 23:41:36 -0500 [thread overview]
Message-ID: <20061130044136.GA9755@butterfly.falsifian.afraid.org> (raw)
In-Reply-To: <c811f84d47f05813f479a07ec1e60478@plan9.bell-labs.com>
On Wed, Nov 29, 2006 at 05:30:40PM -0500, geoff@plan9.bell-labs.com wrote:
> sources is up and I can mount it from inside and outside, with and
> without authentication, though we do get occasional console messages
> like these:
>
> Mon Nov 27 15:16:53: attach main as forsyth: not enough data in auth read
> Mon Nov 27 16:16:12: attach main as forsyth: not enough data in auth read
> Tue Nov 28 09:30:11: attach main as geoff: phase error protocol phase error: read in state SNeedProto
> Tue Nov 28 09:30:13: attach main as geoff: phase error protocol phase error: read in state SNeedProto
> Wed Nov 29 09:30:11: attach main as geoff: phase error protocol phase error: read in state SNeedProto
> Wed Nov 29 09:30:13: attach main as geoff: phase error protocol phase error: read in state SNeedProto
>
> In this case, your connection to sources has dropped, so you need to
> remove /srv/sources, and you'll need to be hostowner to do that if you
> don't own /srv/sources, then execute `9fs sources' again.
Removing /srv/sources worked. Thanks.
- James
next prev parent reply other threads:[~2006-11-30 4:41 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 21:55 james.cook
2006-11-29 22:20 ` Lyndon Nerenberg
2006-11-29 22:30 ` geoff
2006-11-29 22:49 ` Charles Forsyth
2006-11-30 4:41 ` James Cook [this message]
2008-11-02 18:51 Skip Tavakkolian
2008-11-02 19:04 ` Pietro Gagliardi
2008-11-02 21:35 ` geoff
2008-11-02 21:58 ` michael block
2008-11-02 23:46 ` Pietro Gagliardi
2009-05-22 16:34 Rudolf Sykora
2009-05-22 16:51 ` ron minnich
2009-05-22 17:12 ` erik quanstrom
2009-05-22 17:23 ` Rudolf Sykora
2009-05-22 20:52 ` dave.l
2009-05-22 21:15 ` Uriel
2009-05-22 22:13 ` Noah Evans
2009-05-22 22:18 ` Eric Van Hensbergen
2009-05-22 23:06 ` Rudolf Sykora
2009-05-22 23:42 ` Eric Van Hensbergen
2009-05-22 23:54 ` Francisco J Ballesteros
2009-05-23 2:28 ` Anant Narayanan
2009-05-22 21:09 ` Uriel
2009-05-22 21:31 ` ron minnich
2009-05-22 21:43 ` Uriel
2009-05-22 22:59 ` Latchesar Ionkov
2009-05-22 21:05 ` Uriel
2009-05-22 21:13 ` Eric Van Hensbergen
2009-05-23 3:57 ` Skip Tavakkolian
2009-05-23 23:59 ` J.R. Mauro
2009-05-24 0:17 ` ron minnich
2009-05-24 0:28 ` Anant Narayanan
2009-05-24 0:31 ` ron minnich
2009-05-24 23:27 ` David Leimbach
2009-05-24 23:38 ` jt
2009-05-25 0:22 ` Federico G. Benavento
2009-05-25 0:28 ` David Leimbach
2009-05-25 0:44 ` Federico G. Benavento
2009-05-25 6:05 ` andrey mirtchovski
2009-05-25 8:28 ` Rudolf Sykora
2009-05-25 10:07 ` Federico G. Benavento
2009-05-25 10:39 ` cinap_lenrek
2009-05-25 18:27 ` Steve Simon
2009-05-25 19:25 ` J.R. Mauro
2009-05-24 1:59 ` J.R. Mauro
2009-05-24 1:26 ` Lyndon Nerenberg
2015-08-24 16:42 KADOTA Kyohei
2015-08-24 17:02 ` stevie
2015-08-24 18:04 ` KADOTA Kyohei
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=20061130044136.GA9755@butterfly.falsifian.afraid.org \
--to=james.cook@utoronto.ca \
--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).