From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] env walk
Date: Thu, 10 May 2001 14:39:40 +0100 [thread overview]
Message-ID: <20010510133208.2132F199E7@mail.cse.psu.edu> (raw)
> By the way, it's setting all the env's in your example that takes the
> time, not forking in rc. Rc doesn't reread the /env's. If you
> do an iostats on the example you'll see no opens of /env after
> setting the vars:
that's a bit spurious, i'm afraid, because rc opens #e directly so
iostats can't see those accesses.
given that rc does read all the environment variables when it starts
up, i think it's quite likely it's spending a fair amount of time doing
so...
rog.
next reply other threads:[~2001-05-10 13:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-10 13:39 rog [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-10 14:48 rog
2001-05-10 14:41 presotto
2001-05-10 13:49 rob pike
2001-05-10 13:04 presotto
2001-05-10 12:58 presotto
2001-05-09 16:58 presotto
2001-05-09 17:34 ` Sam
2001-05-09 17:39 ` Sam
2001-05-10 8:33 ` Peter Schay
2001-05-09 13:23 presotto
2001-05-09 15:45 ` Peter Schay
2001-05-09 11:54 Peter Schay
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=20010510133208.2132F199E7@mail.cse.psu.edu \
--to=rog@vitanuova.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).