Anyone?
Anyone?
Buehler?
On Fri, Oct 17, 2014 at 9:41 AM, Alan McKay <[email protected]> wrote:
> Hi folks,
>
> The manpage for relayd.conf has this basic construct in it a couple of times :
>
> table <service> { 192.168.1.1, 192.168.1.2, 192.168.2.3 }
> table <fallback> disable { 10.1.5.1 retry 2 }
>
> redirect "www" {
> listen on www.example.com port 80
> forward to <service> check http "/" code 200
> forward to <fallback> check http "/" code 200
> }
>
> And also has this to say about the "disable" attribute.
>
> disable
> The redirection is initially disabled. It can be later enabled
> through relayctl(8).
>
> What I don't understand from the given examples is how "<fallback>"
> above is getting re-enabled. It starts out with the table disabled -
> I get that. But then within the redirect we are basically saying
> (correct me if I am wrong) "always use <service> unless it is not
> availble, in which case use <fallback>"
>
> But I don't see anywhere that <fallback> was re-enabled so how can it
> be used? And I search through the manpage and don't see any mention
> of this. Does it automatically get re-enabled within the "redirect -
> forward"? And if that is the case, what was the point of starting it
> disabled in the first place?
>
> thanks,
> -Alan
>
> --
> "Don't eat anything you've ever seen advertised on TV"
> - Michael Pollan, author of "In Defense of Food"
--
"Don't eat anything you've ever seen advertised on TV"
- Michael Pollan, author of "In Defense of Food"
