headers
Guilherme | 20 Jul 2006 19:19
Picon
Favicon

Problems to get some events

Hello all, I'm a beginner in Dazuko, and I'm having
some problems related to get some events from kernel.
I'm using Freebsd 6.0 and Dazuko 2.2.1. I'm using
example.c, and I get events, in the monitored
directory, when: create a file, change file, remove
directory, but when I create directories and move
files inside of the monitored directory, I don't
identify this... Any idea??

I register the following events:

DAZUKO_ON_OPEN, DAZUKO_ON_CLOSE,
DAZUKO_ON_CLOSE_MODIFIED,  DAZUKO_ON_EXEC,
DAZUKO_ON_UNLINK, DAZUKO_ON_RMDIR

P.S.: I compiled Dazuko with following options: 
  --enable-event-unlink
  --enable-event-rmdir         
  --enable-event-close-modified   

Thanks

		
_______________________________________________________ 
O Yahoo! está de cara nova. Venha conferir! 
http://br.yahoo.com/preview
Permalink | Reply | 1 comment |
headers
John Ogness | 20 Jul 2006 21:23
Favicon

Re: Problems to get some events

Guilherme wrote:
> I get events, in the monitored
> directory, when: create a file, change file, remove
> directory, but when I create directories and move
> files inside of the monitored directory, I don't
> identify this... Any idea??

Dazuko only captures events that are related to
creating/removing/changing file contents. When you move a file within a
directory, you don't actually touch it's contents.

Creating directories also isn't captured (because no one ever wanted it
until now).

However, support for these other types of events are planned for future
versions of Dazuko. But they won't show up until sometime next year.

John Ogness

P.S. It surprises me that you are using 2.2.1. That version has a typo
in the FreeBSD code that causes it not to compile. I assume you either
fixed it yourself, or you are using 2.2.2-pre1 or 2.3.0.

--

-- 
Dazuko Maintainer
Permalink | Reply | 0 comments |
headers
John Ogness | 29 Jul 2006 11:42
Favicon

2.2.2-pre2 posted

Hi,

I have posted a new pre-release for the upcoming 2.2.2 stable version.
Some issues with the upcoming 2.6.18 needed to be resolved (version
headers re-organized, LSM API changed, devfs API disappeared). I also
changed the configure script so that it won't activate RSBAC support
unless "--enable-rsbac" is explicitly given. Auto-detection of RSBAC was
causing too much support since Mandrake includes RSBAC, but doesn't
activate it.

Once 2.2.2 has been released, I will port these changes to the 2.3.x
development. Then a 2.3.1 version should become the next stable version
(once all the 2.3.0 problems have been resolved).

Users should only use 2.3.0 if you need syscall hooking for Linux 2.6.
Most users do not.

John Ogness

--

-- 
Dazuko Maintainer
Permalink | Reply | 0 comments |

Gmane