Re: customizing debian apache
Apparently the path is hardcoded into suexec for "security reasons", so...
Anyway, as Jeremy said (and much to our fustration) the suexec source
included is missing critical files required for compilation, so we grab
the apache source code and just build suexec (think i've mentioned this
before... anyway).
Sincerely,
Jason Lim
----- Original Message -----
From: "Jeremy C. Reed" <reed@wcug.wwu.edu>
To: "Matt Hope" <matth@cse.unsw.edu.au>
Cc: <debian-isp@lists.debian.org>
Sent: Friday, November 09, 2001 11:39 AM
Subject: Re: customizing debian apache
> On Thu, 8 Nov 2001, Matt Hope wrote:
>
> > fairly tidy. An alternative would be patching suexec to accept a
run-time
> > path (from what I gather, this is non-trivial)
>
> The apache-common package comes with some suexec source. But I am not
sure
> why -- since it is unusable because it is missing several more headers.
>
> Anyways, I often use sed to patch suexec:
>
> $ cat -v sed.expression
> s/\/home\/httpd\/html/\/home^@^@^@^@^@^@^@^@^@^@^@/
>
> Jeremy C. Reed
> ......................................................
> ISP-FAQ.com -- find answers to your questions
> http://www.isp-faq.com/
>
>
> --
> To UNSUBSCRIBE, email to debian-isp-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
> http://www.zentek-international.com
>
Reply to: