[ZBXNEXT-1103] Setting ConfigFrequency on a Passive proxy should cause the service to not start Created: 2012 Feb 02 Updated: 2012 Oct 13 |
|
| Status: | Open |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Proxy (P) |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature Request | Priority: | Major |
| Reporter: | Edgar Juarez | Assignee: | Alexei Vladishev |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | validation | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Description |
|
The ConfigFrequency setting when using Passive proxy is misleading and confusing when ProxyConfigFrequency on the Zabbix server should be used instead. Perhaps the proxy should not start if the ConfigFrequency setting is set and send an appropriate message in the proxy log. |
| Comments |
| Comment by richlv [ 2012 Feb 05 ] |
|
same should happen with all other parameters which are not relevant (data sender frequency, heartbeat frequency etc) |
| Comment by Oleksii Zagorskyi [ 2012 Feb 05 ] |
|
I think in this case the error message should sound similar/unified with |