Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should I disable maldet monitoring or not ? #384

Open
mbautista opened this issue May 5, 2021 · 1 comment
Open

Should I disable maldet monitoring or not ? #384

mbautista opened this issue May 5, 2021 · 1 comment

Comments

@mbautista
Copy link

mbautista commented May 5, 2021

Hello,
First thank you for maldet, it's a great tool :)
I just had a few questions about the maldet monitoring service.

We use maldet on our shared web servers that host hundreds of websites, and we set up a nightly scan which works well.
I've just discovered that there was a "monitoring service", if I understood it correctly, this service can listen to modified files and scan them on the fly using inotify.

Currently this service fails to start because inotify-tools is not installed on our servers. I was wondering whether I should fix this or not : if I install inotify-tools and setup the monitor path correctly, then the service would start, but I'm afraid it might consume lots of resources (because it's a shared server with hundreds of websites), I think the nightly scan is sufficient for now.

My questions are :

  • Do you think it's a good practice to disable monitoring on shared servers ?
  • If NO then : Will it consume a lot if I turn it on for all users paths ? Or maybe I could set only specific system path(s) ?
  • If YES then : Can you please indicate a way to properly disable the service without having a "failed" error ?

Thank you for your help :)
Mathieu.

@WilliamDEdwards
Copy link

As inotify is a kernel subsystem, it is efficient. Shouldn't be a problem to use it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants