Minor In Windows, the vfs.file.regmatch function may become ZBX_NOTSUPPORTED.
]# zabbix_get -s 192.168.xxx.xxx -k vfs.file.regmatch["C:\zabbix_agentd.conf","LogFile",cp932] ZBX_NOTSUPPORTED ]# zabbix_get -s 192.168.xxx.xxx -k vfs.file.regmatch["C:\zabbix_agentd.conf","LogFile",cp932,,,1] ZBX_NOTSUPPORTED ]# zabbix_get -s 192.168.xxx.xxx -k vfs.file.regmatch["C:\zabbix_agentd.conf","LogFile",cp932,,1] 0 ]# zabbix_get -s 192.168.xxx.xxx -k vfs.file.regmatch["C:\zabbix_agentd.conf","LogFile",cp932,,10] 1 ]# zabbix_get -s 192.168.xxx.xxx -k vfs.file.regmatch["C:\zabbix_agentd.conf","LogFile",cp932,,2147483647] 1 ]# zabbix_get -s 192.168.xxx.xxx -k vfs.file.regmatch["C:\zabbix_agentd.conf","LogFile",cp932,,2147483648] ZBX_NOTSUPPORTED ]# zabbix_get -s 192.168.xxx.xxx -k vfs.file.regmatch["C:\zabbix_agentd.conf","LogFile",cp932,,4294967295] ZBX_NOTSUPPORTED
Is the sign inverted?
if (NULL == end_line_str || '\0' == *end_line_str) end_line = 0xffffffff; else if (FAIL == is_uint32(end_line_str, &end_line)) goto err; if (start_line > end_line) <-- here! goto err;
I think that it is the influence of correction of ZBX-9605 .