samba 2.0.5a

[Jennifer LaFene]

Hello. I have installed samba 2.0.5a and are using SWAT to configure. This is my first installation and configuration so I'm in the dark. When I went to status and started smbd and nmbd processes I received the following error message:

Couldn't open status file /var/opt/samba/locks/STATUS..LCK

I looked in the /var/opt/samba/locks folder and the only files it contained were the following:

-rw-r--r-- 1 root root 231 Jul 13 10:23 browse.dat
-rw-r--r-- 1 root root 20 Jul 13 10:21 nmbd.pid
-rw-r--r-- 1 root root 20 Jul 13 10:21 smbd.pid

If anyone could share their thoughts on this I would greatly appreciate it. Please feel free to contact me directly if additional information is needed.
Thank you

Jennifer LaFene
303.649.5851
jennifer_lafene@hp.com

[Alan Riggs]

I haven't used SAMBA, but it might be a file creation issue. What are the permissions on the locks directory itself?

[Kofi ARTHIABAH]

Is SWAT running as a super user? or as nobody? is this the entry in your /etc/inetd.conf?

swat stream tcp nowait.400 root /usr/sbin/swat swat

also check the permissions on SWAT.

PS. You might need to touch the lock file...

[Jennifer LaFene]

The permissions on the locks directory are set to the following:
drwxr-xr-x 2 root sys 96 Jul 13 10:49 locks

I am using swat with the server root and password.
I have also in my initial configuration for swat as the following:

swat stream tcp nowait.400 root /opt/samba/bin/swat swat

I will try and touch the STATUS..LCK file and see if this makes any difference.
Thank you

[Jennifer LaFene]

I just went out to http://us4.samba.org/samba/docs and began viewing Samba FAQ and found the answer to my problem.

Couldn't open status file STATUS..LCK

If you run smbstatus before anyone has ever connected to your new
Samba installation then you may get the error:

Couldn't open status file /var/lock/samba/STATUS..LCK

or possibly the error:

ERROR smb_shm_open : open failed with code No such file or directory
ERROR: Failed to initialize share modes!
Can't initialize shared memory - exiting

both of these errors are harmless. The appropriate files and memory
segments get automatically created the first time you connect to
Samba. Try connecting with smbclient and you should find that
smbstatus is happy after your first connection.