We have been trying to get NFS4 ACLs working and this issue greatly
affects us (showstopper for workstation deployment). I can confirm the
bug is fixed in the server kernel image (tried with 2.6.32-27.49), but
is seems to be still unpatched in the generic image (tried version
2.6.32-27.29). When
Can confirm the fix works also for me.
However I do see a change in how username checks are handled. Before the
AssumeDefaultDomain setting worked I could match 'domain\username' in
group and sudo checks without problems. It didn't matter how the
username was actually registered in AD (i.e.
I have now been able to confirm the issue on 2 different machines. Both
having the same problems. 4 hours after caching problems arise. Logons
are no longer possible, getent stops returning information about the AD
users, etc. Strange thing is though that lw-ad-cache --enum-users still
provides
Public bug reported:
Binary package hint: likewise-open
likewise-open 5.4.0.42111-2ubuntu1 on 10.04 64 bit
The CacheEntryExpire setting seems to be ignored. I changed the setting
to: CacheEntryExpiry=dword:0013C680 then imported the registry file
and issued a lw-refresh-configuration. Cleared
Sorry, small typo: CacheEntryExpire should of course be CacheEntryExpiry
--
CacheEntryExpire setting ignored
https://bugs.launchpad.net/bugs/572271
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Can confirm. Caching does not work after a restart.
--
password caching no longer works
https://bugs.launchpad.net/bugs/509934
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: likewise-open
Setting AssumeDefaultDomain=dword:0001 does not work with
likewise-open 5.4.0.39949-3 on Ubuntu 10.04 (development branch) 64 bit.
Steps to reproduce:
1. Install likewise-open, join domain.
2. Check likewise behavior: getent passwd
Can confirm this is still a bug in 9.10 (64 bit) using gnome-screensaver
2.28.0-0ubuntu3.4. Only happens when Likewise reports the users password
is about to expire.
However I agree with comments #3 and #5 as this is a showstopper for AD
integration and adoption of Likewise in enterprises. Many
