From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <ee9e417a0701101015g4553bfc2q9e84fa3533a707cf@mail.gmail.com>
Date: Wed, 10 Jan 2007 13:15:25 -0500
From: "Russ Cox" <rsc@swtch.com>
To: "=?ISO-8859-1?Q?Alberto_Cort=E9s?=" <alcortes@it.uc3m.es>,
	"Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] slow boot, may be a secstore time out
In-Reply-To: <20070110181109.GB25778@it.uc3m.es>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20070110181109.GB25778@it.uc3m.es>
Cc:
Topicbox-Message-UUID: 00c1f11c-ead2-11e9-9d60-3106f5b1d025

> I have a cpu/auth/fs server and a terminal.
>
> The terminal is booting with the server as auth and fs.
>
> When booting the terminal:
>
> - I am asked for a user name.
> - 6 minutes waiting for the next prompt
> - factotum ask me about my username and password for the fs
>   domain with proto p9sk1
> - I get a nice, working terminal
>
>
> A snoopy running on the server during those 6 minutes of waiting
> show some tcp traffic from the client to the server at the
> secstore port.
>
> My server is not a secstore server.
>
> How can I tell factotum not to connect to my (nonexistent)
> secstore server?
>
> I would like to do without a secstore server until I learn
> something about it :).

If you are not running secstore, then a connect to that
port (5356) should just fail immediately.  It sounds like something
else is silently dropping the tcp connect packets or not
letting the rejections come back.

Russ