After some more investigation, I managed to find out that it's because this Samba is using lock files in /var/opt/samba/locks, such as connections.tdb.lck, which regular users can't access.

What I don't get, is how to disable their use?

On another box, using a slightly older version of HP CIFS server (based on Samba 2.2.8), there are no such files.

There are some difference in the lock configuration beetween the two systems, but from their descriptions, there is no obvious one.

Still looking for any clue on how to fix this...

Laurent


Laurent Blume wrote:

This is for HP CIFS Server A.01.11.03 / Samba 2.2.12, on HP-UX 11.0.

I've got a problem with smbstatus: if run as root, it displays everything as expected.
If run as a regular user, it displays only the following:


$ smbstatus
tdb(/var/opt/samba/locks/connections.tdb): Failed to create active lock file
tdb(/var/opt/samba/locks/connections.tdb): Failed to create active lock file
/var/opt/samba/locks/connections.tdb not initialized.
This is normal if an SMB client has never connected to your server.


Of course, plenty of Windows clients have been connecting to that box.
The permissions on the tdb file are the same as the ones on another box, where it works.
And it used to work on that same system, after it was installed.
So I'm not sure where to look...


There is nothing in the log.smbd file since Samba was started, 10 days ago.

Any idea?

-- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba

Reply via email to