You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On large ip pools with many unused IP addresses, the cron job could take a lot of time to complete.
For example, on a /24 network with no computers, it'll take at least 254 seconds.
I think it will block other background task execution by locking the database.
Version
GLPI: 10.0.6 from tarbal
addressing: 3.0.1 from tarbal
To reproduce
Install glpi.
Install addressing plugin.
Enable addressing plugin.
Go to Tools -> IP addressing.
Add a new pool. For example: 192.168.0.1-192.168.0.254.
Set ping free ip to yes.
Go to Setup -> Automatic actions -> UpdatePing.
Press Execute button.
Expected behavior
Ping executes in the background without locking the base.
Ping is done by blocks, not the whole pool at once.
Ping is done in parallel, not in one blocking thread.
Additional
Maybe instead of ping, it's better to use fping?
The text was updated successfully, but these errors were encountered:
Summary
On large ip pools with many unused IP addresses, the cron job could take a lot of time to complete.
For example, on a
/24
network with no computers, it'll take at least 254 seconds.I think it will block other background task execution by locking the database.
Version
GLPI: 10.0.6 from tarbal
addressing: 3.0.1 from tarbal
To reproduce
192.168.0.1-192.168.0.254
.Set ping free ip to yes.
Expected behavior
Additional
Maybe instead of ping, it's better to use fping?
The text was updated successfully, but these errors were encountered: