* Pascal Lalonde (plalo...@overnet.qc.ca) wrote: > Hello, > > I've been playing with relayd lately. There is a behavior which seems > unintuitive and I was wondering if that was a bug or the intended > behavior. > It's the intended behavior but I have been meaning to fix that at some point.
> When I try to disable a host (e.g.: relayctl host disable 10.0.1.101), > and that host is part of more than one table, only the first occurence > gets disabled. I'm testing with relayd from Feb 28th snapshot. > > I would suppose it should disable all occurences, since disabling by ID > already lets you choose specific instances of that host. > > # relayctl show summary > Id Type Name Avlblty Status > 1 redirect test active > 1 table test:8080 active > (3 hosts) > 1 host 10.0.1.101 100.00% up > 2 host 10.0.1.102 100.00% up > 3 host 10.0.1.103 100.00% up > 2 redirect test2 active > 2 table test2:30000 active > (6 hosts) > 4 host 10.0.1.101 100.00% up > 5 host 10.0.1.102 100.00% up > 6 host 10.0.1.103 100.00% up > 7 host 10.0.1.104 100.00% up > 8 host 10.0.1.105 100.00% up > 9 host 10.0.1.106 100.00% up > # relayctl host disable 10.0.1.101 > command succeeded > # relayctl show summary > Id Type Name Avlblty Status > 1 redirect test active > 1 table test:8080 active > (2 hosts) > 1 host 10.0.1.101 disabled > 2 host 10.0.1.102 100.00% up > 3 host 10.0.1.103 100.00% up > 2 redirect test2 active > 2 table test2:30000 active > (6 hosts) > 4 host 10.0.1.101 100.00% up > 5 host 10.0.1.102 100.00% up > 6 host 10.0.1.103 100.00% up > 7 host 10.0.1.104 100.00% up > 8 host 10.0.1.105 100.00% up > 9 host 10.0.1.106 100.00% up > > Thanks in advance!
