From: Alex Efros <powerman@powerman.asdfGroup.com>
Subject: Re: apache2 run script
Date: Fri, 6 Oct 2006 18:57:24 +0300 [thread overview]
Message-ID: <20061006155724.GE7053@home.power> (raw)
In-Reply-To: <Pine.LNX.4.64.0610061143150.14026@e-smith.charlieb.ott.istop.com>
Hi!
On Fri, Oct 06, 2006 at 11:46:29AM -0400, Charlie Brady wrote:
> >exec env -i PATH=$PATH LD_PRELOAD=libREV.so \
> > apache2 -DNO_DETACH -k start -DDOC -DSSL -DFASTCGI # -DPHP4
> ...
>
> I don't see any advantage over:
>
> export LD_PRELOAD=libREV.so
> exec apache2 -DNO_DETACH -k start -DDOC -DSSL -DFASTCGI # -DPHP4
This way there a chance to occasionally add some commands between export
and exec lines. This may result in accessing wrong files in these commands
because of libREV.
> LD_PRELOAD=libREV.so exec apache2 -DNO_DETACH -k start \
> -DDOC -DSSL -DFASTCGI # -DPHP4
Yeah, this is acceptable, but I prefer to have 'exec' word in beginning of line
to make scripts ease to read/understand.
Anyway. Why you dislike `env -i` so much to invent all these alternatives? :)
For me `env` is good small program which doing it small task good enough:
env - run a program in a modified environment
In my ./run I need to 'run a program in a modified environment' so I've
used `env`. What's wrong with this?
--
WBR, Alex.
next prev parent reply other threads:[~2006-10-06 15:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-01 9:29 Mark
2006-10-05 23:58 ` Alex Efros
2006-10-06 6:12 ` Vincent Danen
2006-10-06 14:27 ` Charlie Brady
2006-10-06 14:30 ` Charlie Brady
2006-10-06 15:37 ` Alex Efros
2006-10-06 15:46 ` Charlie Brady
2006-10-06 15:57 ` Alex Efros [this message]
2006-10-06 16:01 ` Paul Jarc
2006-10-06 16:21 ` Alex Efros
2006-10-07 0:15 ` Charlie Brady
2006-10-07 0:23 ` Alex Efros
2006-10-07 18:44 ` Paul Jarc
2006-10-05 23:59 ` Charlie Brady
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=20061006155724.GE7053@home.power \
--to=powerman@powerman.asdfgroup.com \
/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).