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

GNU Parallel Semaphores Added #10

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

GNU Parallel Semaphores Added #10

wants to merge 1 commit into from

Conversation

waja
Copy link
Contributor

@waja waja commented Jun 30, 2014

First go ahead with semaphores for LMD. Using GNU's parallel program (perl
threads with file locking) we are able to parallelize the file scanning
process which is the bottleneck in this process.

Users can pass in the number of threads at run by the -a param:
maldet -a /home/?/public_html 15
This will run 15 thread scans.....^^

With one test case pass, I suspect more bugs exists in this implementation. So
far that one test cases includes scanning the /tmp directory where no hits
were found. In addition, the test case was not branch coverage so some if /
logic statements were never ran.

The downfall of using semaphores within bash is variable scope -- they need to
be exported into the environment. This is where most bugs will be introduced.

Signed-off-by: Adam Brenner [email protected]

First go ahead with semaphores for LMD. Using GNU's parallel program (perl
threads with file locking) we are able to parallelize the file scanning
process which is the bottleneck in this process.

Users can pass in the number of threads at run by the -a param:
    maldet -a /home/?/public_html 15
This will run 15 thread scans.....^^

With one test case pass, I suspect more bugs exists in this implementation. So
far that one test cases includes scanning the /tmp directory where no hits
were found. In addition, the test case was not branch coverage so some if /
logic statements were never ran.

The downfall of using semaphores within bash is variable scope -- they need to
be exported into the environment. This is where most bugs will be introduced.

Signed-off-by: Adam Brenner <[email protected]>
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

Successfully merging this pull request may close these issues.

2 participants