Fixed Linux PIDs casting & added posibility to "disable" check from config. #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
AbstractProcessMonitor
so that it can properly handle situations wherePMonitorNbOfProcesses
key inappSettings
is set to0
or missing completly. This would be useful when it is desired to disable the check without redeploying the application that uses this library. I encountered a situation where it would have been helpful to disable the check in order to partial restore application functionality until I would figure out the issue causing the library to fail. Leading to the next change:LinuxProcessStatusFile
but without thePid
andFileName
being set at all. Furthermore, the check is done on theLinuxProcessStatusFile
being instantiated but its properties are never verified.GetProcessName
method which attempts to trim theLinuxProcessStatusFile.FileName
property just to end up in throwing aNullReferenceException
:null
when theLinuxProcessStatusFile
cannot be sucessfully build instead of an object but with invalid values.