search for: tdb_clear_if_first

...vailable to the Samba community for wider testing. Common bugs fixed in this preview release include: o Crash bugs and change notify issues in Samba''s printing code. o Honoring secondary group membership on domain member servers. o TDB scalability issue surrounding the TDB_CLEAR_IF_FIRST flag. New features introduced in this preview release include: o Improved support for i18n character sets. o Support for account lockout policy based on bad password attempts. o Improved support for long password changes (>14 characters) and strong password enforcement....

...vailable to the Samba community for wider testing. Common bugs fixed in this preview release include: o Crash bugs and change notify issues in Samba''s printing code. o Honoring secondary group membership on domain member servers. o TDB scalability issue surrounding the TDB_CLEAR_IF_FIRST flag. New features introduced in this preview release include: o Improved support for i18n character sets. o Support for account lockout policy based on bad password attempts. o Improved support for long password changes (>14 characters) and strong password enforcement....

Hi all, Please excuse me if this question is not appropriate for this forum: Lets assume that samba server crashed or was shut down abnormally, while users where holding open files in the server. In this case, I've noticed that locking.tdb is not being cleaned when samba is restarting. I was wondering why shouldn't it be cleaned. Thanks, Nir

Hi, Does someone know a document which explains the TDB structure. functionalites, and format of the TDB files etc. I need to understand why some of the TDBs like messages.tdb, unexpected.tdb, brlock if not read_only, locking.tdb, session.tdb, wins.tdb are called with TDB_CLEAR_IF_FIRST tdb flags. Why some TDBs are opend with O_RDWR|O_CREAT flags viz. gencache.tdb, group_mapping.tdb, account_policy.tdb, share_info.tdb, secrets.tdb. schannel_store.tdb etc. etc. why registry.tdb is uniquely been tried to open with O_RDWR flag and if fails then tried with O_RDWR|O_CREAT flag. and...

...e "Changes" section for details on exact updates. Common bugs fixed in Samba 3.0.3 include: ~ o Crash bugs and change notify issues in Samba''s ~ printing code. ~ o Honoring secondary group membership on domain member ~ servers. ~ o TDB scalability issue surrounding the TDB_CLEAR_IF_FIRST ~ flag. ~ o Substitution errors for %[UuGg] in smb.conf. ~ o winbindd crashes when using ADS security mode. ~ o SMB signing errors. ~ o Delays in winbindd startup caused by unnecessary ~ connections to trusted domain controllers. ~ o Various small memory leaks. ~ o Winbindd failing due...

...e "Changes" section for details on exact updates. Common bugs fixed in Samba 3.0.3 include: ~ o Crash bugs and change notify issues in Samba''s ~ printing code. ~ o Honoring secondary group membership on domain member ~ servers. ~ o TDB scalability issue surrounding the TDB_CLEAR_IF_FIRST ~ flag. ~ o Substitution errors for %[UuGg] in smb.conf. ~ o winbindd crashes when using ADS security mode. ~ o SMB signing errors. ~ o Delays in winbindd startup caused by unnecessary ~ connections to trusted domain controllers. ~ o Various small memory leaks. ~ o Winbindd failing due...

Does anyone have any idea what can cause nmbd to begin gobbling CPU? We are running Samba 2.2.4 on HP-UX 10.20, having upgraded from Samba 2.0.10 about a month ago. Our clients are a mixture of NT 4.0 and Win2K. Today, we have begun to see widespread client drive disconnections, and nmbd is averaging 60%+ CPU usage with peaks up to 100%. We have heard reports of network problems at our site