printing, locking, etc in 2.2.0

Neil Hoggarth neil.hoggarth at
Mon May 21 14:28:20 GMT 2001

On Fri, 11 May 2001 12:43:08 -0400 Jeremy Allison <jeremy at>

> We don't use lock files. These may be dead entries in the
> lock database, but these will get deleted once other smbds
> notice the pids are dead.
> I'll review the code though just to be sure.

Hi Jeremy

Did you ever get around to this review? I'm seeing a "phantom" lock,
owned by an smbd process that bailed out several hours ago, and it
doesn't appear that the remaining smbds are going going to break it or
clear it up of its own accord.

I'm running 2.2 CVS, checked out yesterday afternoon, on Solaris 2.6.

The smbd process that bailed out with the following log messages:

[2001/05/21 11:44:28, 0, pid=29514] lib/util_sock.c:write_socket_data(542)
  write_socket_data: write failure. Error = Broken pipe
[2001/05/21 11:44:28, 0, pid=29514] util_sock.c:write_socket(566)
  Error writing 989 bytes to socket 4: ERRNO = Broken pipe
[2001/05/21 11:44:28, 0, pid=29514] util_sock.c:send_smb(753)
  Error writing 989 bytes to client. -1. Exiting

It looks like the client went away unexpectedly, and smbd decided to

Is there any way to manually delete an entry from the locking database?

Neil Hoggarth                                 Departmental Computer Officer
<neil.hoggarth at>                   Laboratory of Physiology                  University of Oxford, UK

More information about the samba-technical mailing list