Comment 21 for bug 572271

Thank you Marc for posting your PPA. I restarted the lsassd service after upgrading to the ppa6 version and now the "Cache entry expiry" shows the hex changes I've made using lw-edit-reg.

-- Before --
Event Record ID......... 155
Event Table Category.... System
Event Type.............. Information
Event Date.............. 2010-06-08
Event Time.............. 09:46:22 AM
Event Source............ Likewise LSASS
Event Category.......... Service
Event Source ID......... 1004
Event User.............. SYSTEM
Event Computer.......... sps31-728-ckr1
Event Description....... Likewise authentication service provider configuration settings have been reloaded.

     Authentication provider: lsa-activedirectory-provider
     Current settings are...
     Cache reaper timeout (secs): 2592000
     Cache entry expiry (secs): 14400

-- After --
Event Record ID......... 162
Event Table Category.... System
Event Type.............. Information
Event Date.............. 2010-06-08
Event Time.............. 10:45:44 AM
Event Source............ Likewise LSASS
Event Category.......... Service
Event Source ID......... 1004
Event User.............. SYSTEM
Event Computer.......... sps31-728-ckr1
Event Description....... Likewise authentication service provider configuration settings have been reloaded.

     Authentication provider: lsa-activedirectory-provider
     Current settings are...
     Cache reaper timeout (secs): 2592000
     Cache entry expiry (secs): 2592000

I really hope this bug fix can receive some priority escalation for release Lucid production updates. LW is very cool software and a provides real opportunity to get more business users on Ubuntu. Not being able to take an Likewise-open enable Ubuntu LTS laptop off the Active Directory network for less than a few hours is a basic failure for enterprise users.

Gerald, Marc, please let me know if there is any additional testing I can do to help move things along.