similar to: locking.tdb - Failed to open byte range locking database

does anyone know how to hide a samba server in SMB terms? on an NT machine the command "net config server /hidden:yes" will make the machine vanish from the network neighbourhood but i cant figure out how to do this for a samba server many thanks sincerely, bob reven

Hi! I've been fighting with Samba for over a week now and I can't seem to work it out. It all started when I installed the standard samba (2.2.1a-4) which came with RH7.2. I ran "smbstatus" and got the following error: Failed to open byte range locking database ERROR: Failed to initialise locking database Can't initialise locking module - exiting. I've tried the

(Yes, I should upgrade Samba to 3.0.35). We're running the Sun provided Samba daemon (SUNWsmbau and friends) on Solaris 10 Generic_138888-08 (sparc). Lots of Windows clients (mixed XP, 2003, 2008) hit this server and periodically we'll start seeing smbd processes begin piling up. These processes can't be killed with a normal kill -- only kill -9 will do the trick. In the past

On Sat, Apr 22, 2006 at 06:15:31PM +0100, Daniel J Blueman wrote: > As a test, I changed the opening of the locking.tdb and brlock.tdb > files to use the TDB_INTERNAL flag, avoiding use of the fcntl(F_SETLK) > syscall for locking individual database records. Performance was a lot > snappier, with quite a bit less system time used. > > What is the scope of implementing shared

I have successfully implemented Samba in the past but I am now perplexed by a new installation which fails smbstatus with the message: "tdb((null)): tdb_open_ex: could not open file /var/cache/samba/brlock.tdb: No such file or directory Failed to open byte range locking database "tdb((null)): tdb_open_ex: could not open file /var/cache/samba/locking.tdb: No such file or directory ERROR:

Hi all, i am trying to run Samba 2.2.3a under a RedHat 7.2 i386 machine. After i compiled and installed the packages, i made a smb.conf up. Just some standard stuff nothing special. Now, when i start smbd and then check it with smbstatus it gives me this error : Samba version 2.2.3a Service uid gid pid machine ---------------------------------------------- tdb((null)): tdb_open_ex: could not

We've just gone live with a file & print server, and are having major problems with Samba. When used out of hours, with all PCs switched on and connected to the domain, everything works fine. However, during the day, we have problems where users can't print to any samba-hosted printer, Access database applications (where the database is held on the server) won't work, or work

I am getting this error message when I type smbstatus.The message does not offer a lot of assistance. Is there any one with a good reason for this message?? Thx in advance Glenn Samba version 2.2.0a Service uid gid pid machine ---------------------------------------------- Failed to open byte range locking database ERROR: Failed to initialise

I'm running 2.11, and I've noticed a number of log entries that look like so: angie.log: tdb(/usr/local/samba/var/locks/locking.tdb): expand_file ftruncate to 8192 failed (Permission denied) [2004/10/03 15:14:36, 0] tdb/tdbutil.c:tdb_log(531) tdb(/usr/local/samba/var/locks/brlock.tdb): expand_file ftruncate to 8192 failed (Permission denied) The files in question look like this:

In /varcache/samba/ I have several .tdb files. Like brlock.tdb, locking.tdb, ntdrivers.tdb, etc. Excusing my ignorance, what are these files, and what do they do? And why must they be copied when migrating from one samba server to a new one?

On Sat, Apr 22, 2006 at 06:15:31PM +0100, Daniel J Blueman wrote: > I did some smbd profiling, and was seeing quite a lot of time spent > (un)locking [1] TDB files. > > A quick workload of opening a few directory trees, we see a _lot_ of > activity with a few TDB files: > > locking.tdb: 11943 accesses > brlock.tdb: 690 accesses > group_mapping.tdb: 126 accesses >

[2799/3801] Compiling source3/locking/locking.c [2800/3801] Compiling source3/locking/brlock.c ../source3/locking/brlock.c: In function 'brl_get_locks_readonly_parser': ../source3/locking/brlock.c:2071: error: expected expression before 'struct' ../source3/locking/brlock.c:2071: warning: assignment makes pointer from integer without a cast ../source3/locking/brlock.c: In function

Hello, I've found this issue reported only once before but no real answer was provided/found. I am trying to migrate from an old 2.0.7 server, but the bundled install 3.0.24 on FC6 is giving me major pain. Putting aside the actual configuration and user migration which I need to figure out, the problem is that nmbd refuses to start with the following errors in the log: [2007/02/26 14:05:26,

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,

Hello, I have been tracking this bug as much as possible, and it appears there is a severe problem in the code that deals with .tdb files. Lately our samba 2.2 testbed has been having painfully slow network responsiveness. It would go 30-60 seconds without a response to a client on many occasions (both browsing the network, and opening files/refreshing directories). Clients include Windows 98se,

When using Samba 3.0.23b (slightly old, I know) on CentOS 4.4, smbstatus -B fails with a segmentation fault. smbstatus works, and tdbdump is able to dump brlock.tdb and locking.tdb without any errors (which is not what I expected). Here's the backtrace (non-ASCII characters replaced with 'X'): #0 0x0017fa2c in memcpy () from /lib/tls/libc.so.6 #1 0x0029b19f in tdb_write

Hi all, i am trying to run Samba 2.2.3a under a RedHat 7.2 i386 machine. After i compiled and installed the packages, i made a smb.conf up. Just some standard stuff nothing special. Now, when i start smbd and then check it with smbstatus it gives me this error : Samba version 2.2.3a Service uid gid pid machine ---------------------------------------------- tdb((null)):

When I start winbindd (Samba v2.2.3a on Linux), I get the entries in log.winbindd shown below. What's the story on all those complaints about file "unexpected.tdb"? There is no general problem with Samba writing to that subdirectory: # ll /var/lock/samba/ total 288 -rw-r--r-- 1 root root 696 Feb 12 22:01 brlock.tdb -rw-r--r-- 1 root root 231 Feb 13

Hi, I see samba with ctdb locking has following mapping when kernel oplocks = yes. share mode reservations = flock(2) posix byte range locking = fcntl(2) SMB locks (mandatory) = ctdb using brlock.tdb oplocks = fcntl(2) using F_SETLEASE Am I correct or I am missing something? I hope only SMB range locks are implemented with tdb, all else are being used from filesystem. What

I am using CALDERA OPENLINUX 3.1.1 with latest patches and Samba 2.2.5 on it. But recently I start to receive linux error "kernel: VFS MAX FILES REACHED" and Samba error "Too many open files". After it I tuning linux increase open files descriptors in /etc/security/limits.conf * soft nproc 4094 * hard nproc 16384 * soft