[PATCH] make smbstatus exit without error when no connections ever happened to a server

Christian Perrier bubulle at debian.org
Thu Oct 4 04:12:09 GMT 2007

This patch is about to celebrate its 5th birthday in Debian..:-)

It fixes Debian bug #161489:

From: Janos Holanyi <csani at lme.linux.hu>
To: Debian Bug Tracking System <submit at bugs.debian.org>
Subject: smbstatus: Can't initialise locking module - exiting
Date: Thu, 19 Sep 2002 15:55:15 +0200

Package: samba
Version: 2.999+3.0cvs20020906-1
Severity: normal
Tags: upstream


until no clients are connected, I get the following behavior from 'smbstatus':

# smbstatus 
sessionid.tdb not initialised

Service      pid     machine       Connected at
Failed to open byte range locking database
ERROR: Failed to initialise locking database
Can't initialise locking module - exiting
# echo $?

However, there is no error. As soon as somebody connects, disconnects, there is
no 'Can't initialise locking module - exiting' error any more:

# smbstatus 

Samba version 2.999+3.0cvs20020906-1 for Debian
PID     Username      Group         Machine                        

Service      pid     machine       Connected at
No locked files
# echo $?

To be honest, I haven't tried to reproduce that behaviour with current
versions. Just wanted to avoid keeping that patch in Debian for 5 more
years as we had to slightly adapt it for 3.2.0pre1 builds.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smbstatus-locking.patch
Type: text/x-diff
Size: 936 bytes
Desc: not available
Url : http://lists.samba.org/archive/samba-technical/attachments/20071004/fabcafff/smbstatus-locking.bin

More information about the samba-technical mailing list