From: Michael Stewart <gentoo@insaneone.com>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Setting an env var for a specific ebuild
Date: Sun, 31 Oct 2004 10:22:27 -0800 [thread overview]
Message-ID: <41852D63.2030709@insaneone.com> (raw)
In-Reply-To: <20041031170225.GA28023@tripadelic.com>
Sri Gupta wrote:
>>Apache uses a wrapper called suexec to run setuid cgi programs. As
>>part of its security check, suexec refuses to run any program whose
>>location does not match a compiled-in path, which by default is
>>.../public_html/... Note that this path is NOT picked up from the run
>>time configuration, but from the build time configuration.
>
> I have the same problem, and usually edit the ebuild every upgrade.
> I haven't found a more graceful way to change the suexec path.
I am currently working on a fix for this. You may track it's progress at
http://bugs.gentoo.org/show_bug.cgi?id=66397
~vericgar
--
gentoo-portage-dev@gentoo.org mailing list
prev parent reply other threads:[~2004-10-31 18:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 20:02 [gentoo-portage-dev] webapp-config and webapps Wendall Cada
2004-10-28 20:20 ` Paul de Vrieze
2004-10-28 20:34 ` Wendall Cada
2004-10-28 20:55 ` Wendall Cada
2004-10-28 21:19 ` Stuart Herbert
2004-10-28 21:28 ` Stuart Herbert
2004-10-28 21:13 ` Stuart Herbert
2004-10-28 21:48 ` Anthony Gorecki
2004-10-28 22:13 ` Stuart Herbert
2004-10-28 22:52 ` Anthony Gorecki
2004-10-28 23:31 ` Stuart Herbert
2004-10-29 1:04 ` Anthony Gorecki
2004-10-29 9:55 ` Paul de Vrieze
2004-10-30 10:17 ` Stuart Herbert
2004-10-30 21:24 ` Paul de Vrieze
2004-10-28 20:52 ` Grant Goodyear
2004-10-31 16:38 ` [gentoo-portage-dev] Setting an env var for a specific ebuild felix
2004-10-31 17:02 ` Sri Gupta
2004-10-31 18:22 ` Michael Stewart [this message]
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=41852D63.2030709@insaneone.com \
--to=gentoo@insaneone.com \
--cc=gentoo-portage-dev@lists.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