Skip to content

Feature/nfs exclusion v2 #547

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

Merged
merged 10 commits into from
Feb 19, 2015
Merged

Conversation

reyjrar
Copy link
Member

@reyjrar reyjrar commented Feb 13, 2015

This implements the <skip_nfs>yes</skip_nfs> option in rootcheck and syscheck. Since it's available, it also warns if a user attempts to iNotify on an NFS partition as that is not supported by iNotify.

Micha Nasriachi and others added 8 commits February 13, 2015 15:00
Conflicts:
	src/rootcheck/check_rc_sys.c
NFS mounts are scanned.  The defaults do scan NFS mounts, which is
consistent with existing functionality.

Conflicts:
	src/config/rootcheck-config.c
	src/rootcheck/check_rc_sys.c
Conflicts:
	src/config/syscheck-config.c
	src/syscheckd/config.c
	src/syscheckd/create_db.c
the define back and removed trailing whitespace.

Conflicts:
	src/Makefile
using a struct[] to handle the flags we want to skip if
<skip_nfs>yes</skip_nfs> which makes adding new entries easier.

Idea stolen from @jrossi and brutally mutalated by me.
debugging messages to ensure code paths are being followed.
jrossi added a commit that referenced this pull request Feb 19, 2015
@jrossi jrossi merged commit 79b5b5f into ossec:master Feb 19, 2015
@reyjrar reyjrar deleted the feature/nfs_exclusion_v2 branch February 19, 2015 09:21
@jrossi
Copy link
Member

jrossi commented Feb 19, 2015

@reyjar could you add some documentation for this? With docs I feel people will get lost with this feature.

@reyjrar
Copy link
Member Author

reyjrar commented Apr 18, 2015

Added documentation on : ossec/ossec-docs#94

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

Successfully merging this pull request may close these issues.

2 participants