public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "leon j. breedt" <ljb@neverborn.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] rc-scripts speedup
Date: Sun, 20 Apr 2003 12:39:17 +1200	[thread overview]
Message-ID: <20030420003917.GB32124@jeddah.neverborn.ORG> (raw)
In-Reply-To: <1050776776.3688.6.camel@ndiin>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, Apr 19, 2003 at 11:26:16AM -0700, Eric Andresen wrote:
> Whoops, I was posting from the wrong address.
> 
> Two things.. using a few methods of making LC_ALL=C for grep/awk only,
> none of them had any significant change in startup time one way or the
> other.
> 
> Second, wouldn't it be a lot easier to just alias grep and awk to
> "LC_ALL=C grep" and likewise for awk within runscript.sh?
well, i went for the all-out approach, and replaced every invocation
with LC_ALL=C <cmd>, and did the export LC_ALL=C before all occurences
of "x start|stop". it felt a bit faster..i'm going to revert to the
existing rc-scripts and see if i can feel a difference.

have you tried using the rc-scripts i attached to the bug report?

i don't think just exporting LC_ALL=C in just one place is sufficient, i'm
sure it gets dropped on the floor a few times.

also, will an alias be inherited by everything thats executed down the
line?

leon

- -- 
in the beginning, was the code.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+oew1RWcl5mzp4f4RAphEAJ0QU/cF2yG8DL5s2BoEVWcUYw2XagCeMv3m
Tg/7SqGpWaVaflTTLWO/PW8=
=L6VK
-----END PGP SIGNATURE-----

--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-04-20  0:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-19 10:57 [gentoo-dev] rc-scripts speedup leon j. breedt
     [not found] ` <1050776776.3688.6.camel@ndiin>
2003-04-20  0:39   ` leon j. breedt [this message]
2003-04-20  5:03     ` [gentoo-dev] rc-scripts speedup - or not :/ leon j. breedt
2003-04-20  8:20       ` Joseph Carter

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=20030420003917.GB32124@jeddah.neverborn.ORG \
    --to=ljb@neverborn.org \
    --cc=gentoo-dev@gentoo.org \
    /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