From: byron@netapp.com (Byron Rakitzis)
To: rc@hawkwind.utcs.toronto.edu
Subject: speed of rc
Date: Tue, 13 Apr 1993 16:26:04 -0400 [thread overview]
Message-ID: <9304132026.AA15743@netapp.netapp.com> (raw)
John pointed out to me that the rc path search does a stat() before
an exec(), even for an absolute path name. Optimizing out that
stat should take care of the "pus" problem, if indeed that file
is full of lines which say "/tmp/xx".
Disclaimer: I haven't tried to reproduce any of this stuff here yet.
Further disclaimer: I want to offer my apologies for not spending
more time on rc, but things have really never been busier for me
as a programmer.
next reply other threads:[~1993-04-13 20:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-04-13 20:26 Byron Rakitzis [this message]
1993-04-13 21:23 ` John Mackin
1993-04-13 23:42 ` mycroft
-- strict thread matches above, loose matches on Subject: below --
1993-04-15 20:26 Tom Culliton x2278
1993-04-12 5:51 Speed " Paul Haahr
1993-04-09 15:58 Tom Culliton x2278
1993-04-08 23:09 Paul Haahr
1993-04-08 22:31 Tom Culliton x2278
1993-04-09 0:38 ` Scott Schwartz
1993-04-09 15:23 ` John Mackin
1993-04-13 19:26 ` Chris Siebenmann
1993-04-13 21:13 ` John Mackin
1993-04-09 16:32 ` Dave Mason
1993-04-09 16:39 ` John Mackin
1993-04-09 19:22 ` Dave Mason
1993-04-09 21:12 ` Chris Siebenmann
1993-04-08 20:14 Byron Rakitzis
1993-04-08 15:45 Paul Haahr
1993-04-07 19:50 Tom Culliton x2278
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=9304132026.AA15743@netapp.netapp.com \
--to=byron@netapp.com \
--cc=rc@hawkwind.utcs.toronto.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).