proc.num with cmdline parameter broken in 1.4?

[StanZoid]

I have an environment where any of a small number of binaries is run many times for different db schemas. The cmdline option of proc.num, which worked well in 1.1.7, does not work in 1.4 that I can tell. Here is one of many examples:

ps -ef returns (among other debit processes):
apps 6254 1 0 05:26 ? 00:00:00 /usr/apps/common/debit wp
apps 6255 1 0 05:26 ? 00:00:00 /usr/apps/common/debit wp

zabbix_get -s bourne -p 10050 -k proc.num[debit]
45

zabbix_get -s bourne -p 10050 -k proc.num[debit,,,]
45

zabbix_get -s bourne -p 10050 -k proc.num[debit,,,wp]
0 (Should be 2)

When using the cmdline parameter:
The 1.1.7 server asking the 1.1.7 agent gets the correct answer
The 1.4 server asking the 1.4 agent gets the wrong answer
The 1.1.7 server won't return data from the 1.4 agent other than ZBXD
The 1.4 server times out trying to get this info from the 1.1.7 agent

I would love to get this fixed so I can put 1.4 into production--it's great!
StanZoid

[Alexei]

Thanks for reporting this! Fixed, the patch is attached.

[StanZoid]

Awesome! The patch works as advertised at the agent side. Your quick and excellent response to my dilemma is really appreciated.

By the way--very nice rework of the interface! It feels tighter and flows better in a number of areas. I'm still debating whether I like the change to rows so they no longer double up if they don't fit the width of the window.

My implementation time in the 1.4 environment, starting from scratch, will probably take 2/3 the time of the original even after moving all of the items, triggers, etc to templates and adding a number of machines and network devices to the mix.

Great job!
Stanzoid