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
Can you implement processor limit on the log4j scan run, perhaps as an option in commandline?
I am aware that BigFix is having this capability built in, i have used it for four years on the environment, but we have moved from BigFix in favour of Ansible and Ansible does not sport a client, that would limit the processor time used by the job.
I would be happy if you would be able to do such limit on all platforms we support (aix, linux, windows), but the priority is based on a customer request on Linux now.
The text was updated successfully, but these errors were encountered:
Can you implement processor limit on the log4j scan run, perhaps as an option in commandline?
I am aware that BigFix is having this capability built in, i have used it for four years on the environment, but we have moved from BigFix in favour of Ansible and Ansible does not sport a client, that would limit the processor time used by the job.
I would be happy if you would be able to do such limit on all platforms we support (aix, linux, windows), but the priority is based on a customer request on Linux now.
The text was updated successfully, but these errors were encountered: