Re: [Pound Mailing List] poundctl command simply do not work

It would appear I'm not the only one to run into and document this exact
problem:

https://groups.google.com/forum/#!msg/pound_proxy/s_OZhTcznRc/nq_HqNMjFwcJ


On Tue, Jun 18, 2013 at 9:37 AM, Brad Allison <[email protected]>wrote:

> I'm trying to use the -b option for poundctl to disable a backend.
>
> The command runs with the three fields listener service and backend.  The
> command appears to work.
>
> But when I list out the -X option it says all backends are enabled... even
> though I just disabled it.  So the options for poundctl do not work.
>
> Notice how the status for the backend index=1 it still set to "active"
> after I disabled it.
>
> [root@ ~]# /usr/sbin/poundctl  -c /var/lib/pound/pound.cfg -b 0 0 1
>
> [root@ ~]# /usr/sbin/poundctl  -c /var/lib/pound/pound.cfg -X
> <pound>
> <listener index="0" protocol="HTTPS" address="0.0.0.0:443"
> status="active">
> </listener>
> <service index="0">
> <backend index="0" address="10.0.2.21:443" avg="0.000" priority="5"
> alive="yes" status="active" />
> <backend index="1" address="10.0.3.22:443" avg="0.000" priority="5"
> alive="yes" status="active" />
> <session index="0" key="demo.lalala.com" backend="1" />
> <session index="1" key="107.11.11.11" backend="1" />
> </service>
> </pound>
>
>