Hi, Thanks for that however i don't think that is the parameter which i am after, basically i want to increase the timeout which looks like this when you run a net cache list :
Key: IDMAP/SID2UID/S-1-5-21-1587460048-1370446368-1630864436-16176 Timeout : Wed Jan 13 15:29:11 2010 Value: 423047 the above key is almost a week old and once it expires the only way to fix it is to flush the cache, however the cache is not regenerated correctly (incorrect gids) and the only way i can fix this is to rename the idmap config inside smb.conf, flush the cache again, run a getent passwd to populate the cache, then rename idmap config back and restart smb and winbind.. then its ok for a week... 2010/1/12 Gaiseric Vandal <[email protected]> > On 01/12/10 10:58, Wasim Bashir wrote: > >> Hi, >> >> Is there a way of changing the default idmap caching ? I believe it is >> current set to 1 week. I am using samba 3.3.9. >> >> Also any ideas why when this cache expires it does not renew which means I >> have to do a net cache flush to clear the cache ? >> >> Thanks in advance. >> >> >> Wasim >> >> > If should be the "idmap cache time" parameter in smb.conf. But I have > the same problem with Samba 3.0.x on Solaris 10. From my testing it looks > like samba 3.4.x behaves better. > > > I was not aware oif the "net cache flush" command- so I may add that as a > cron job to my samba 3.0.x systems. > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
