httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Houser, Rick" <>
Subject RE: [users@httpd] Rookie Question on Define and Testing the value
Date Tue, 31 May 2016 19:42:27 GMT
I currently specify the variables I want to check as flags from whatever logic I want external
to the httpd binary, then test for the existence of the appropriate flag using IfDefine. 
For example, I replaced apachectl with a custom version that can determine which datacenter
I'm running in and adds the appropriate -D definitions to the httpd startup, etc. 

Rick Houser
Web Administration

> -----Original Message-----
> From: Eric Covener []
> Sent: Tuesday, May 31, 2016 15:38
> To:
> Subject: Re: [users@httpd] Rookie Question on Define and Testing the value
> On Tue, May 31, 2016 at 3:32 PM, Darryl Philip Baker
> <> wrote:
> > I’m trying to do some conditional configuration settings. I know that I can
> > use “Define variable value” to set up a variable. I know that “<IfDefine
> > [!}variable>” can be used to test to see if a variable is set or not. I
> > looked at “<If expression>” as a possibility but since what I am setting
> > really configuration change and “If” is a runtime directive. Using “If”
> > going to add runtime overhead for something that will not change for the
> > life of the daemon. Is there initialization directive to use to see if a
> > variable set using “Define” matches a particular value and what is that
> > directive if it exists?
> I don't think you can test against their values in something like
> <IfDefine -- you can only currently do a boolean <ifDefine> and inside
> get at the value with ${VAR}.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

View raw message