Re: [ossec-list] syscheck not working with restrict option

Should we expect to be solved in the forthcoming ossec release? El viernes, 29 de enero de 2016, 20:17:46 (UTC+1), Daniel Cid escribió: > > Awesome :) > > On Fri, Jan 29, 2016 at 3:06 PM, Luke Hansey > wrote: > >> Works great now. Thank you for the work on this.

Re: [ossec-list] syscheck not working with restrict option

Awesome :) On Fri, Jan 29, 2016 at 3:06 PM, Luke Hansey wrote: > Works great now. Thank you for the work on this. No worries about the > time. It's developmental :) Plus, I have a little firmer grasp on OSSEC > now. > > On Thursday, January 28, 2016 at 4:58:11 PM

Re: [ossec-list] syscheck not working with restrict option

Works great now. Thank you for the work on this. No worries about the time. It's developmental :) Plus, I have a little firmer grasp on OSSEC now. On Thursday, January 28, 2016 at 4:58:11 PM UTC-8, Daniel Cid wrote: > > The issue was in my branch there. Mind getting the latest again? Should

Re: [ossec-list] syscheck not working with restrict option

The issue was in my branch there. Mind getting the latest again? Should be working now: https://bitbucket.org/dcid/ossec-hids/get/tip.tar.gz Sorry for the waste of time :/ thanks, On Thu, Jan 28, 2016 at 1:34 PM, Luke Hansey wrote: > Thanks for the reply, Santiago.

Re: [ossec-list] syscheck not working with restrict option

Are you sure your config is not working? I just tested this and it works for me: /root I created three test files: root@vpc-ossec-manager:~# ls test.txt* test.txt1 test.txt2 test.txt3 And this is what I get in my syscheck file: root@vpc-ossec-manager:~# cat

[ossec-list] syscheck not working with restrict option

If I use: /var/www/vhosts/ syscheck logs no changes to any file. If I use: /var/www/vhosts/ Works fine and logs changes to any file. Am I missing something when using the *restrict *option? -- --- You received this message because you are subscribed to the Google Groups "ossec-list"