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 [thread overview]
Message-ID: <e1d4626b2e3e995a1060e2bd52732a0d@granite.cias.osakafu-u.ac.jp> (raw)
>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
next reply other threads:[~2002-07-18 0:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 0:14 okamoto [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-19 5:34 forsyth
2002-07-18 13:22 presotto
2002-07-29 15:58 ` Don
2002-07-18 10:42 forsyth
2002-07-18 9:12 forsyth
2002-07-17 22:40 okamoto
2001-07-18 22:20 okamoto
2001-07-18 15:52 okamoto
2001-07-15 17:56 okamoto
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=e1d4626b2e3e995a1060e2bd52732a0d@granite.cias.osakafu-u.ac.jp \
--to=okamoto@granite.cias.osakafu-u.ac.jp \
--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).