Adding my thoughts to this.

Basically the smbsharedmodes manner of working, as of now, will not work for 
any other service/protocol provider to have shared locking semantics with SAMBA 
(unless they are GPLv3 themselves). As without registering the unique ID, any 
other service that wants to register locks in the SAMBA database for cross 
protocol locking to function, will not be feasible.

I would think the intention for having the shared locking database and the 
library (smbsharedmodes) would be to enable this functionality, across SAMBA 
and other file services that need file locking of this nature. Hence the 
ability to register the unique ID would also fall under this bucket of things 
to provide.

With this in mind, would it be possibly to (re)consider how the unique ID 
registration can be modified, so that other services can leverage the inherent 
locking that smbsharedmodes is providing to play nice in a SAMBA + other 
protocol serving needs environment?

Regards,
Shyam
 
>>> Manoj Dahal 1/25/2012 05:12 PM >>> 
Hi Volker,
 
An alternate thought came into mind.
Is it possible for you or someone from Samba to write a simpler serverid.c code 
without cluster support?
Which can possibly be bundled in a new library or in libsmbsharemodes.so under 
LGPL.
So that it will have lesser licensing issues. 
 
Thanks,
 
-Manoj

>>> Volker Lendecke <volker.lende...@sernet.de> 1/24/2012 7:06 PM >>>
On Tue, Jan 24, 2012 at 06:31:59AM -0700, Manoj Dahal wrote:
> Thanks a lot again. Is it possible for you to let us know
> the other authors/contributors
> of serverid.c ? So that we can obtain their approval as well.

You can find them with "git log serverid.c".

With best regards,

Volker Lendecke

-- 
SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax: +49-551-370000-9
AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
http://www.sernet.de, mailto:kont...@sernet.de
.

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Reply via email to