Problems with SAMBA 2.2.2 Locking Databases Running on HP-UX 11.00 64 Bit

[Drew.Zeller at statcan.ca]

Hi,

I posted this message a few days ago, but have not heard anything yet.  If
anyone could provide any assistance with this it would be greatly
appreciated.

Thanks

> -----Original Message-----
> Sent:	Tuesday, December 04, 2001 10:16 PM
> To:	'samba at lists.samba.org'
> Subject:	*X* Problems with SAMBA 2.2.2 Locking Databases Running on
> HP-UX 11.00 64 Bit
> 
> Hi,
> 
> I have been trying to get Samba 2.2.2 to run on HP-UX 11.00 64 bit, but
> seem to be running into problems with the locking databases. (Note : this
> is running the smb.conf file from the examples directory in SAMBA 2.2.2).
> I have tried to two different servers and both of them generate the same
> result described below.
> 
> 
> The problem I have hit is after compiling samba and starting up the system
> I found that I could not access any of my shares.  When I try to  run the
> smbstatus command I receive the following error :
> 
> ./smbstatus
> 
> Samba version 2.2.2
> Service      uid      gid      pid     machine
> ----------------------------------------------
> 
> Failed to open byte range locking database
> ERROR: Failed to initialise locking database
> Can't initialise locking module - exiting
> 
> 
> I tried checking the log files, but there was nothing there (even when I
> sent the debug level to 10).
> 
> As for the /usr/local/samba/var/locks directory, here is the list of files
> present :
> 
> -rw-r--r--   1 root       sys            371 Dec  4 22:08 browse.dat
> -rw-r--r--   1 root       root          8192 Dec  4 21:43 connections.tdb
> -rw-------   1 root       root           696 Dec  4 21:43 messages.tdb
> -rw-r--r--   1 root       sys             20 Dec  4 21:43 nmbd.pid
> -rw-r--r--   1 root       root            20 Dec  4 21:43 smbd.pid
> -rw-r--r--   1 root       sys          16384 Dec  4 22:08 unexpected.tdb
> 
> When I checked in the source directory I discovered that a core file had
> been created after I had run the configure script there.
> 
> 
> Anyone have any ideas?
> 
>