Re: [9fans] time to accept swap

Re: [9fans] time to accept swap

[okamoto]

>is it possible it's attempting to connect to the wrong authentication server address?

When I put explicit name to cpu command, say 
term% cpu -h diabase
I got the same result.   /env/cpu says it's diabase, and it's correct.
I suppose this may be connected to the slow authentication when
mounting other filesystem. (?)

Kenji

Re: [9fans] time to accept swap

[Don]

I had this same problem on a Thinkpad 760L I installed as
an auth server. Logins would take forever waiting to be
authenticated. As soon as I remembered to turn on swap
(by adding 'swap /dev/sdC0/swap' in my cpurc) this problem
disappeared. At the same time lagged logins started to
appear the console would stop responding to keys typed on
the keyboard. However CTRL+ALT+DEL would still HUP the
machine. I never got around to figuring out why any of
this happened since swap fixed the issue.
Don

Re: [9fans] time to accept swap

[forsyth]

[-- Attachment #1: Type: text/plain, Size: 291 bytes --]

yes, it was doing a DNS query to try to resolve the invented domain.
you could make /lib/ndb/local authoritative for that domain, and then
you could use the domain as you like.   it has been years since i
last had to do ndb from scratch, but i think
	dom=<fake domain> soa
will do it.

[-- Attachment #2: Type: message/rfc822, Size: 1909 bytes --]

From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] time to accept swap
Date: Thu, 19 Jul 2001 00:52:20 +0900
Message-ID: <a4ec8763ddeab53d0da319bf1d074ebc@granite.cias.osakafu-u.ac.jp>

>% ndb/csquery
>> net!$auth!ticket

term% net!$auth!ticket
> net!$auth!ticket
/net/tcp/clone 192,.168.1.11!567

I see no problem from this answer???

By the way, from the hints by Charles and Dave, I re-examined my
/lib/ndb/local file, and found a line

auth=diabase.<fake domain> authdom=<fake domain>

where <fake domain> should be read replaced by something.

Then, I changed the line to

auth=diabase authdom=<fake domain>

Now, the slow authentication problem is gone.

Thanks all!

Kenji

Re: [9fans] time to accept swap

[presotto]

[-- Attachment #1: Type: text/plain, Size: 240 bytes --]

Do the following:

% ndb/csquery
> net!$auth!ticket

See what the result is.  Then try conning to each one in
turn and see if that's what's slow.  The typical problem is
to try a protocol first that the other side isn't listening on.

[-- Attachment #2: Type: message/rfc822, Size: 5720 bytes --]

[-- Attachment #2.1.1: Type: text/plain, Size: 87 bytes --]

is it possible it's attempting to connect to the wrong authentication server address?

[-- Attachment #2.1.2: Type: message/rfc822, Size: 4079 bytes --]

[-- Attachment #2.1.2.1.1: Type: text/plain, Size: 175 bytes --]

When I dispatch 'cpu' command, it takes about a minute to
authenticate.   I must be doing something bad,
but how am I?  Authentication itself is done correctly...

Kenji

[-- Attachment #2.1.2.1.2: Type: message/rfc822, Size: 2189 bytes --]

From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: [9fans] time to accept swap
Date: Mon, 16 Jul 2001 02:56:05 +0900
Message-ID: <73f5d3410cc615100e7aba9a31218420@granite.cias.osakafu-u.ac.jp>

I noticed that neccessary time to authentication is somewhat long,
several seconds in our case, when attach the swap area from other
file system on the file server.   Is this a normal behaviour?

Our network:

Auth/CPU server:  1.6 GHz Pen 4, RTL8100BL nic chip
File server: 200MHz AMD K6, Intel i82557 nic chip
Terminals:  many, most with nvidia graphic cards, and 
			i82557 + 2114x nic chip
		Thanks Mirtchovski updating nvidia driver.   I cannot live
		without those two files over 1024x768x8 resolutions, even
		MX 200 etc.

Kenji

Re: [9fans] time to accept swap

[forsyth]

[-- Attachment #1: Type: text/plain, Size: 199 bytes --]

sorry, i meant attemting to connect to the wrong address to
authenticate the connection, not connecting
to the wrong server for the cpu.
have you got auth and authdom settings in /lib/ndb/local?

[-- Attachment #2: Type: message/rfc822, Size: 1724 bytes --]

From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] time to accept swap
Date: Thu, 18 Jul 2002 09:14:13 +0900
Message-ID: <e1d4626b2e3e995a1060e2bd52732a0d@granite.cias.osakafu-u.ac.jp>

>is it possible it's attempting to connect to the wrong authentication server address?

When I put explicit name to cpu command, say 
term% cpu -h diabase
I got the same result.   /env/cpu says it's diabase, and it's correct.
I suppose this may be connected to the slow authentication when
mounting other filesystem. (?)

Kenji

Re: [9fans] time to accept swap

[forsyth]

[-- Attachment #1: Type: text/plain, Size: 87 bytes --]

is it possible it's attempting to connect to the wrong authentication server address?

[-- Attachment #2: Type: message/rfc822, Size: 4079 bytes --]

[-- Attachment #2.1.1: Type: text/plain, Size: 175 bytes --]

When I dispatch 'cpu' command, it takes about a minute to
authenticate.   I must be doing something bad,
but how am I?  Authentication itself is done correctly...

Kenji

[-- Attachment #2.1.2: Type: message/rfc822, Size: 2189 bytes --]

From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: [9fans] time to accept swap
Date: Mon, 16 Jul 2001 02:56:05 +0900
Message-ID: <73f5d3410cc615100e7aba9a31218420@granite.cias.osakafu-u.ac.jp>

I noticed that neccessary time to authentication is somewhat long,
several seconds in our case, when attach the swap area from other
file system on the file server.   Is this a normal behaviour?

Our network:

Auth/CPU server:  1.6 GHz Pen 4, RTL8100BL nic chip
File server: 200MHz AMD K6, Intel i82557 nic chip
Terminals:  many, most with nvidia graphic cards, and 
			i82557 + 2114x nic chip
		Thanks Mirtchovski updating nvidia driver.   I cannot live
		without those two files over 1024x768x8 resolutions, even
		MX 200 etc.

Kenji

Re: [9fans] time to accept swap

[okamoto]

[-- Attachment #1: Type: text/plain, Size: 175 bytes --]

When I dispatch 'cpu' command, it takes about a minute to
authenticate.   I must be doing something bad,
but how am I?  Authentication itself is done correctly...

Kenji

[-- Attachment #2: Type: message/rfc822, Size: 2189 bytes --]

From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: [9fans] time to accept swap
Date: Mon, 16 Jul 2001 02:56:05 +0900
Message-ID: <73f5d3410cc615100e7aba9a31218420@granite.cias.osakafu-u.ac.jp>

I noticed that neccessary time to authentication is somewhat long,
several seconds in our case, when attach the swap area from other
file system on the file server.   Is this a normal behaviour?

Our network:

Auth/CPU server:  1.6 GHz Pen 4, RTL8100BL nic chip
File server: 200MHz AMD K6, Intel i82557 nic chip
Terminals:  many, most with nvidia graphic cards, and 
			i82557 + 2114x nic chip
		Thanks Mirtchovski updating nvidia driver.   I cannot live
		without those two files over 1024x768x8 resolutions, even
		MX 200 etc.

Kenji

Re: [9fans] time to accept swap

[okamoto]

[-- Attachment #1: Type: text/plain, Size: 305 bytes --]

>	dom=<fake domain> soa
>will do it.

I already have this line in my /lib/ndb/local, but it doen't allow me
to use

auth=diabase.<fake domain> authdom=<fake domain>

instead of

auth=diabase authdom=<fake domain>

Kenji  --just returned from the jouney ^_^ getting dual Pen2 motherboard. :-)

[-- Attachment #2: Type: message/rfc822, Size: 4136 bytes --]

[-- Attachment #2.1.1: Type: text/plain, Size: 291 bytes --]

yes, it was doing a DNS query to try to resolve the invented domain.
you could make /lib/ndb/local authoritative for that domain, and then
you could use the domain as you like.   it has been years since i
last had to do ndb from scratch, but i think
	dom=<fake domain> soa
will do it.

[-- Attachment #2.1.2: Type: message/rfc822, Size: 1909 bytes --]

From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] time to accept swap
Date: Thu, 19 Jul 2001 00:52:20 +0900
Message-ID: <a4ec8763ddeab53d0da319bf1d074ebc@granite.cias.osakafu-u.ac.jp>

>% ndb/csquery
>> net!$auth!ticket

term% net!$auth!ticket
> net!$auth!ticket
/net/tcp/clone 192,.168.1.11!567

I see no problem from this answer???

By the way, from the hints by Charles and Dave, I re-examined my
/lib/ndb/local file, and found a line

auth=diabase.<fake domain> authdom=<fake domain>

where <fake domain> should be read replaced by something.

Then, I changed the line to

auth=diabase authdom=<fake domain>

Now, the slow authentication problem is gone.

Thanks all!

Kenji

Re: [9fans] time to accept swap

[okamoto]

>% ndb/csquery
>> net!$auth!ticket

term% net!$auth!ticket
> net!$auth!ticket
/net/tcp/clone 192,.168.1.11!567

I see no problem from this answer???

By the way, from the hints by Charles and Dave, I re-examined my
/lib/ndb/local file, and found a line

auth=diabase.<fake domain> authdom=<fake domain>

where <fake domain> should be read replaced by something.

Then, I changed the line to

auth=diabase authdom=<fake domain>

Now, the slow authentication problem is gone.

Thanks all!

Kenji

[9fans] time to accept swap

[okamoto]

I noticed that neccessary time to authentication is somewhat long,
several seconds in our case, when attach the swap area from other
file system on the file server.   Is this a normal behaviour?

Our network:

Auth/CPU server:  1.6 GHz Pen 4, RTL8100BL nic chip
File server: 200MHz AMD K6, Intel i82557 nic chip
Terminals:  many, most with nvidia graphic cards, and 
			i82557 + 2114x nic chip
		Thanks Mirtchovski updating nvidia driver.   I cannot live
		without those two files over 1024x768x8 resolutions, even
		MX 200 etc.

Kenji