fix: use correct env var names in memguardian init

[AmSach]

Fixed incorrect env var names used in memguardian init() function.

Bug: The init() function was using the wrong env var names:

• was reading instead of
• was reading instead of

Fix: Changed both to use their respective, correctly-named env vars.

Before:

DefaultInterval = env.GetEnvOrDefault(MemGuardianMaxUsedRamRatioENV, time.Duration(time.Second*30))
maxRam := env.GetEnvOrDefault(MemGuardianMaxUsedRamRatioENV, )

After:

DefaultInterval = env.GetEnvOrDefault(MemGuardianIntervalENV, time.Duration(time.Second*30))
maxRam := env.GetEnvOrDefault(MemGuardianMaxUsedMemoryENV, )

This ensures that the documented env vars ( and ) actually work as intended.

[neo-by-projectdiscovery-dev]

Neo - PR Security Review

No security issues found

_{Comment @pdneo help for available commands. · Open in Neo}