search for: unwish

All, I wonder if someone can give me an idea what the file "netsamlogon_cache.tdb" contains... as I have noticed that I can be added to a group, and access will not appear on the Unix side for a good deal of time... but if I stop Winbind, remove the file "netsamlogon_cache.tdb", and re-start everything, it will then work. Can anyone tell me what the purpose of this file is,

...esperately need is a config-file option (or some automatic mechanism if initrd image is not found on the disk) to show a prompt and wait for a key PRIOR to loading the initrd image. This way I could use plain syslinux and don't need to use 'hacked' Distros bootdisks with plenty of other unwished effects builtin. Ideally prompting and the message should be configurable, maybe even on a by image basis, but that's only cosmetical. BUT: There should be a way to stop and wait for a key AFTER loading the kernel but BEFORE loading the initrd. I'm under the impression you can't do...

I have 4 Samba 4.7.0 DCs. I have 3 clients using samba-winbind.x86_64 0:4.6.2-11.el7_4 with an identical configuration, which produce inconsistent user group membership for multiple users. I've tried using all 4 DCs explicitly (e.g., realm = dc01.mediture.dom), net cache flush and restarting winbind. I've also tested cloning a user and setting up the user as identical as possible:

...omain controller correctly calculates the user's group memberships authoritatively and makes the information available to the Samba server. This is the only reliable way Samba can get informed about the groups a user is member of. Because of its flakiness, the fallback group membership code is unwished, and our code pathes try hard to only use of the group memberships calculated by the domain controller. However, a lot of admins rely on the fallback behavior in order to support access for nfs access, ssh public key authentication and passwordless sudo. That's the reason for changing this...

...omain controller correctly calculates the user's group memberships authoritatively and makes the information available to the Samba server. This is the only reliable way Samba can get informed about the groups a user is member of. Because of its flakiness, the fallback group membership code is unwished, and our code pathes try hard to only use of the group memberships calculated by the domain controller. However, a lot of admins rely on the fallback behavior in order to support access for nfs access, ssh public key authentication and passwordless sudo. That's the reason for changing this...

...y > calculates the user's group memberships authoritatively and makes the > information available to the Samba server. This is the only reliable > way Samba can get informed about the groups a user is member of. > > Because of its flakiness, the fallback group membership code is unwished, > and our code pathes try hard to only use of the group memberships > calculated by the domain controller. > > However, a lot of admins rely on the fallback behavior in order to support > access for nfs access, ssh public key authentication and passwordless > sudo. > >...