Samba 4 and winbind
Rowland Penny
repenny at f2s.com
Mon Apr 15 12:11:19 MDT 2013
On 15/04/13 18:55, Alexander Bokovoy wrote:
>
>
>
> On Mon, Apr 15, 2013 at 8:47 PM, Rowland Penny <repenny at f2s.com
> <mailto:repenny at f2s.com>> wrote:
>
> On 15/04/13 18:23, Alexander Bokovoy wrote:
>>
>>
>>
>> On Mon, Apr 15, 2013 at 7:12 PM, Rowland Penny <repenny at f2s.com
>> <mailto:repenny at f2s.com>> wrote:
>>
>> On 15/04/13 16:47, Jeremy Allison wrote:
>>
>> On Mon, Apr 15, 2013 at 04:42:50PM +0100, Rowland Penny
>> wrote:
>>
>> Again, this I understand, but if Winbind was a stand
>> alone daemon,
>> like it is with S3, then you could choose to use it
>> or not. I
>> actually think that if there was a choice then most
>> people would
>> choose not to use winbind due to its complexity and
>> inconsistency.
>>
>> Oh, bitching on winbindd again. Very popular on this list it
>> seems :-).
>>
>> If you have specific problems, please log bugs. Don't just
>> try and make some specific code into the boogyman, we've
>> had enough of proprietarty vendors doing that against the
>> whole of Samba thanks very much, we don't need our own users
>> to join in.
>>
>> Jeremy.
>>
>>
>> OK, do you really want me to log a bug that basically says
>> that because S3 & S4 winbinds are different and the fact that
>> you cannot get the same uidNumber on the server as on the
>> clients that winbind is broken!!
>>
>> Yes, I do want you to log this bug. There is no reason why
>> winbind implementation in Samba AD DC should use unpredictable
>> and dependent on the order of allocations high watermark algorithm.
>
> Could you please write this again in English, specifically the
> last part.
>
> Please file a bug about ID mapping in Samba AD DC winbind being
> different from ID mapping in previous Samba versions.
OK, I will file a bug, but could you please advise me what 'the order of
allocations high watermark algorithm' means in English, I do understand
it at all.
Rowland
>
> Thanks in advance.
> --
> / Alexander Bokovoy
>
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
More information about the samba-technical
mailing list