In message <[EMAIL PROTECTED]> "David E. Cross" writes:
: Ok... I have *had* it with the meta, but not really, lockd. Are there any
: kernel issues with correctly implimenting rpc.lockd? How can I take a
: filehandle and map it into a filename, with path, so I may open it and lock
: it on the server? Are there any protocol specs? I downloaded the RFC for
: version 4 nlm (which we do not supoprt at *all*), but it only lists diffs to
: the version 3 spec, which I cannot find, and the source is not a whole lot
: of help on this issue.
One area that Solbourne had lots and lots of problems with years ago
when it tried to implenent rpc.lockd was that Sun, at the time, has 5!
incompatible versions that had to be interoperated with. Don't know
if things have changed in the ensuing years or not...
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
