9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Skip Tavakkolian <9nut@9netics.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Problem with drawterm.exe: "cpu: failed to chdir"
Date: Sun, 10 Jun 2007 15:39:22 -0700	[thread overview]
Message-ID: <6ee4a59b0c062436c611627c49b507f3@9netics.com> (raw)
In-Reply-To: <bfdb2cad0706101509j593454a5se7909992f29bbeac@mail.gmail.com>

> That was acutualy what happened. It just took 5 minutes and the first time I
> gave it so long was while I was writing to 9fans.
> Any idea why it takes 5 minutes for it to work?

i don't think chdir is causing the delay. do you have anything in
your $home/lib/profile that could take time when you sign in?



  reply	other threads:[~2007-06-10 22:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-10 21:53 Patrick Kristiansen
2007-06-10 21:59 ` erik quanstrom
2007-06-10 22:09   ` Patrick Kristiansen
2007-06-10 22:39     ` Skip Tavakkolian [this message]
2007-06-10 23:13       ` Patrick Kristiansen
2007-06-10 22:54     ` erik quanstrom

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=6ee4a59b0c062436c611627c49b507f3@9netics.com \
    --to=9nut@9netics.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).