/ Zope / Apsis / Pound Mailing List / Archive / 2007 / 2007-09 / disabling a backend - any indication that this has been done?

[ << ] [ >> ]

[ [patch] Custom Redirect Types / "Chris ... ] [ sticky session with 3 way pound - a little gotcha ... ]

disabling a backend - any indication that this has been done?
Alex Hunsley <alex.hunsley(at)blueyonder.co.uk>
2007-09-24 12:27:32 [ FULL ]
My current pound status, as given by poundctl, is as follows:

pound-front (pid 9518 9517) is running...

  0. http Listener 217.30.114.205:80 a
 -1. Global services
    0. Service active (10)
      0. Backend PF_INET 192.168.37.3:81 active (5 0.000 sec) alive
      1. Backend PF_INET 192.168.37.3:82 active (5 0.000 sec) alive
      0. Session 37355fb9 -> 0
      1. Session 372d5d0a -> 0


I would like to disable the backend number 1, so the command to do this is:

  poundctl -c /var/lib/pound/pound-front.cfg -b 0 0 1

However, if I then look at the poundctl status output, there is no 
difference. Should I see some indication here that a backend has been 
disabled? Just looking for confirmation that my backend-disabling 
command had some effect.....

thanks!
Alex

MailBoxer