<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Patricio Bruna V wrote:
<blockquote cite="mid1111151338.3308.2.camel@cluster2" type="cite">
<pre wrap="">El jue, 17-03-2005 a las 17:02 -0500, Daniel Phillips escribió:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Patricio,
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">Perhaps you meant, how does your program ask for a lock? Or how does
DLM get a lock from a nonlocal machine? From userspace, you go through
a library that presents an interface similar to ancient Vaxcluster, and
later, IBM's OpenDLM. (But somewhat more complex because of the
hierarchical locks feature and a few other wrinkles.) These API calls
are translated into socket messages to and from the in-kernel DLM. The
local DLM consults its lock directory to find out which machine masters
the lock and requests the lock from that machine, which then tries to
get the lock based on its knowledge of current holders, if any.
Does that answer your question?
</pre>
</blockquote>
<pre wrap=""><!---->Daniel,
thx for the answer, but i have another question.
Its necesary that the programs be build agains or with the dlm api?
because if they need to, i dont see the benefits of dlm.
</pre>
</blockquote>
My understanding of DLM is that it sits above the standard FCNTL locks,
and with DLM in place, the locks are cluster wide with the standard
locking APIs. I do not know if DLM works with flock though.<br>
<br>
Mike<br>
</body>
</html>