search for: tdb_lock_bystring

...2.2.7a on a Solaris 8 server with the GCC 2.95.3 version compiler. I get the following compilation warnings. Can i still use the software without a expected crash? Compiling passdb/secrets.c passdb/secrets.c: In function `secrets_named_mutex': passdb/secrets.c:287: warning: passing arg 2 of `tdb_lock_bystring' discards qualifiers from pointer target type Compiling lib/system.c lib/system.c: In function `sys_readdir': lib/system.c:331: warning: return from incompatible pointer type Compiling lib/fsusage.c lib/fsusage.c: In function `sys_fsusage': lib/fsusage.c:127: warning: passing arg 2 o...

..../configure --with-ldapsam --libdir=/usr/local/lib --includedir=/usr/local/include which came back with no problems to speak of. So I ran make, and it came up with Compiling passdb/secrets.c passdb/secrets.c: In function `secrets_named_mutex': passdb/secrets.c:287: warning: passing arg 2 of `tdb_lock_bystring' discards qualifiers from pointer target type Compiling passdb/pass_check.c Compiling passdb/smbpassfile.c Compiling passdb/machine_sid.c Compiling passdb/pdb_smbpasswd.c Compiling passdb/pampass.c Compiling passdb/pdb_tdb.c Compiling passdb/pdb_ldap.c passdb/pdb_ldap.c:48: lber.h: No such file...

...: assignment discards `const' from pointer target typ e Compiling tdb/tdbutil.c tdb/tdbutil.c: In function `tdb_chainlock_with_timeout': tdb/tdbutil.c:46: warning: passing arg 1 of `tdb_set_lock_alarm' discards `volat ile' from pointer target type tdb/tdbutil.c: In function `tdb_lock_bystring': tdb/tdbutil.c:73: warning: assignment discards `const' from pointer target type tdb/tdbutil.c: In function `tdb_unlock_bystring': tdb/tdbutil.c:87: warning: assignment discards `const' from pointer target type tdb/tdbutil.c: In function `tdb_fetch_int32_byblob': tdb/tdbutil.c:...

...no data attached, and a non existent entry 30) Ensure we register the 1c name on the unicast subnet. 31) Fix inheritance problem when recursively setting ACLs on directories 32) prevent ACL set on read-only share 33) Ensure we never have more than MAX_PRINT_JOBS in a queue 34) Added timeout to tdb_lock_bystring() 35) Ensure we set FIRST+LAST flags on a bind request 36) Add version strings to the usage message for smbcacls and smbpasswd 37) Fix bug in the write cache code 38) make the default printed values for boolean the same for all parameters

I have a Linux machine running Samba 2.2.1a (dated, I know) as a domain controller for Windows clients (NT and 2000). I can add NT machines to the domain just fine; I use useradd and smbpasswd to generate the appropriate entries, and it works fine. I tried doing the same thing with a couple of 2000 (SP3) machines, and although I'm allowed to join the domain, after rebooting and trying to log

...ing rpc_client/cli_login.c Compiling rpc_client/cli_trust.c Compiling locking/locking.c Compiling locking/brlock.c Compiling locking/posix.c Compiling passdb/passdb.c Compiling passdb/secrets.c passdb/secrets.c: In function `secrets_named_mutex': passdb/secrets.c:287: warning: passing arg 2 of `tdb_lock_bystring' discards qualifiers from pointer target type Compiling passdb/pass_check.c Compiling passdb/smbpassfile.c Compiling passdb/machine_sid.c Compiling passdb/pdb_smbpasswd.c Compiling passdb/pampass.c Compiling passdb/pdb_tdb.c Compiling passdb/pdb_ldap.c Compiling passdb/pdb_nisplus.c Compiling p...

....c Compiling smbd/ssl.c Compiling lib/talloc.c Compiling tdb/spinlock.c Compiling tdb/tdbutil.c tdb/tdbutil.c: In function `tdb_chainlock_with_timeout': tdb/tdbutil.c:46: warning: passing arg 1 of `tdb_set_lock_alarm' discards qualifiers from pointer target type tdb/tdbutil.c: In function `tdb_lock_bystring': tdb/tdbutil.c:73: warning: assignment discards qualifiers from pointer target type tdb/tdbutil.c: In function `tdb_unlock_bystring': tdb/tdbutil.c:87: warning: assignment discards qualifiers from pointer target type tdb/tdbutil.c: In function `tdb_fetch_int32_byblob': tdb/tdbutil.c:10...

Hello, We are using machines with Solaris and Windows XP. The XP machines are joined in a domain(windows 2003) and the Solaris machines are not joined to any domain. With Samba 2.2.8a running on Solaris 9 there are no problems to access them form Windows XP. We are authenticated by DC. On other machines we have Solaris 10 with Samba 3.0.21b and here we are NOT authenticated anymore by DC. So we