RE: [Dazuko-help] Dazuko 2.3.4 and FreeBSD 6.2

[Mark W. de Raad]

Hello John,

Thank you kindly for your response. We will try the versions below and
let you know when the issue started and version (it may take us a few
days).

Also thanks for the information about the CLOSE_MODIFIED. 

If you (or another reader) have time for a question, our purpose is:

> Monitor a directory of files
> Notice any file changes within that directory
> Initialise a replication process (separate program)

We were hoping to use CLOSE_MODIFIED to only trap the files that have
changed (apart from simply being accessed).

Regarding the move of CLOSE_MODIFIED to the userland, would you
recommend storing the file information in a database? DB2? Mysql?

I presume trigger a process whenever a CLOSE event is trapped (we do not
always seem to get OPEN events for some reason, particularly when data
is appended to a file)

We would also need to generate a checksum I presume - would you
recommend CRC or MD5? (speed is a factor of course).

I am not asking you to solve the problem for us of course! But I am
curious if you have any pointers to how we might implement
CLOSE_MODIFIED type technology in the userspace, rather than us
inventing completely our own systems.

Thanks again.

Mark
---
Mark de Raad
Systems
I-Nex Corporation Pty Ltd

-> Level 1, 88 Flinders Street, Adelaide, South Australia
-> GPO Box I-Nex, Adelaide, SA, 5001, Australia
-> Phone: (08) 8236 7456
-> Fax: (08) 8236 7444
-> Web: http://www.I-NexCorporation.com/ 

-----Original Message-----
From: John Ogness [mailto:address@hidden 
Sent: Tuesday, 5 February 2008 6:02 AM
To: address@hidden; address@hidden
Cc: Mark W. de Raad
Subject: Re: [Dazuko-help] Dazuko 2.3.4 and FreeBSD 6.2

On 2008-02-04, Mark W. de Raad <address@hidden> wrote:
> 1. We are attempting to use Dazuko 2.3.4 on a FreeBSD 6.2 machine
> without success.
> 
> However, when the example code monitors a directory - i.e. a home
> directory in /usr/home (not a symlink), the system either (a) hangs,
> or (b) errors with a kernel panic.
> 
> The kernel panic says: lockmgr: thread 0x... not exclusive lock
> holder 0x ...

Could you try the various versions after 2.3.2? That would make it
easier to isolate the version that introduced the problem.

http://www.dazuko.org/files/dazuko-2.3.3-pre1.tar.gz
http://www.dazuko.org/files/dazuko-2.3.3-pre2.tar.gz
http://www.dazuko.org/files/dazuko-2.3.3-pre3.tar.gz
http://www.dazuko.org/files/dazuko-2.3.3.tar.gz
http://www.dazuko.org/files/dazuko-2.3.4-pre1.tar.gz
http://www.dazuko.org/files/dazuko-2.3.4-pre2.tar.gz
http://www.dazuko.org/files/dazuko-2.3.4-pre3.tar.gz


> 2. Dazuko 2.3.2 on FreeBSD 6.2 machine works, but does not return
> ON_CLOSE_MODIFIED events.

The ON_CLOSED_MODIFIED event is no longer implemented. It is
recommended that the userland application take care of this. Some
information on this topic was mentioned on in the Savannah support
items:

http://savannah.nongnu.org/support/?func=detailitem&item_id=103486

John Ogness

-- 
Dazuko Maintainer