Why are trapper processes etc limited to 255? Couldn't I fork off 500?
Ad Widget
Collapse
Why 255?
Collapse
X
-
Tags: None
-
It is theoretically possible. You would need to change the line in the server.c file which retrieves the values from the conf file which is around line 204. This entry sets up the lower and the upper bounds. Some child processes keep track of their number and often this number is an unsigned char which as a maximum value of 255, though it looks like the trapper threads don't do this.
You can give it a try but you are doing so at your own risk unless you take the time to research what's really going on. Unfortunately a very bad habit is used in places where it shouldn't and that's Global Variables. Also don't be too surprised if you end up banging your head against the wall to understand the code as it tends to lack informative comments. I've griped about this for about 3-4 years, but I wonder if it's done like that to make it harder for anyone else to do something like what Firescope did.RHCE, author of zbxapi
Ansible, the missing piece (Zabconf 2017): https://www.youtube.com/watch?v=R5T9NidjjDE
Zabbix and SNMP on Linux (Zabconf 2015): https://www.youtube.com/watch?v=98PEHpLFVHM
-
I will have to see how it goes....... I've got a huge system with a lot of horsepower and I'd like to avoid getting into a node based setup due to the bugs with it.
Comment
-
Pollers I think are limited to 255 due to a tracking of poller threads using an unsigned char.RHCE, author of zbxapi
Ansible, the missing piece (Zabconf 2017): https://www.youtube.com/watch?v=R5T9NidjjDE
Zabbix and SNMP on Linux (Zabconf 2015): https://www.youtube.com/watch?v=98PEHpLFVHM
Comment
Comment