RE: [Pound Mailing List] Start Service or Backend Disabled

You are, in fact, correct.  There's a missing () in the Disabled regex.

I apologize to whoever reported something like this before, it may be my other branches have this fixed.  But I tend to prefer Enabled instead of Disabled, so my branch is inherently different.

I've updated the stage for upstream branch and added it to pcidss/v2.6, since it is legitimately a bug.

Update and recompile and you should be set.

And yes, you're welcome to use the OrURLs bits as they're in the branch you're using!



Joe

> -----Original Message-----
> From: Felix Zachlod [mailto:fz.lists-oP5Ihzt5Rmkk+I/[email protected]]
> Sent: Wednesday, August 07, 2013 9:27 AM
> To: [email protected]
> Subject: [Pound Mailing List] Start Service or Backend Disabled
> 
> Hello!
> 
> We are currently reworking our pound Setup and we were wondering about
> the functionality oft he Disabled Keyword in the Service and in The
> Backend Section.
> We want our Pound instances come up with certain Backends disabled, we
> want to change the status later on for maintenance purposes but it
> simply seems neither to work within the Service nor within the Backend
> section. Pound does always start with all services or backends in
> "active" state, verified with poundctl. We can enable or disable
> services with poundctl without a problem but we don't get pound running
> with services that are disabled from the beginning. Our config looks
> like follows:
> 
> ######################################################################
> ## global options:
> 
> User            "www-data"
> Group           "www-data"
> 
> LogFacility     local0
> LogLevel        3
> 
> ## check backend every X secs:
> Alive           30
> 
> Control "/var/run/pound/XXX.socket"
> ######################################################################
> 
> ListenHTTPS
>         Address 10.X.X.X
>         Port    443
>         Cert "/etc/pound-shared/ssl[..]"
> 	[...]
>         Service
>             HeadRequire "Host XXXXX"
>             BackEnd
>                         Address 127.0.0.1
>                         Port    81
>                         TimeOut 60
>             End
>             Disabled 1
>         End
> 
> [...]
> 
> After Startup poundctl reports:
> 
> Requests in queue: 0
>   0. HTTPS Listener 10.X.X.X:443 a
>     0. Service active (5)
> 	[...]
>     4. Service active (5)
>       0. Backend 127.0.0.1:81 active (5 0.000 sec) alive [...]
> 
> We are running the version from here:
> 
> https://github.com/goochjj/pound/tree/stage_for_upstream/v2.7b
> 
> Cause we want to use the new feature OrURLs
> 
> Can anybody confirm this behaviour?
> 
> Can anybody tell if we are doing something wrong?
> 
> Thanks in advance
> Felix
> 
> 
> --
> To unsubscribe send an email with subject unsubscribe to
> [email protected]
> Please contact [email protected] for questions.

--
To unsubscribe send an email with subject unsubscribe to [email protected]
Please contact [email protected] for questions.