Add smbstatus test (lock file with smbclient)

Andreas Schneider asn at
Wed Mar 13 14:53:23 UTC 2019

On Wednesday, March 13, 2019 3:02:25 PM CET Ralph Böhme wrote:
> Hi Andreas
> Am 13.03.2019 um 12:08 schrieb Andreas Schneider via samba-technical <samba-
technical at>:
> > I've created a patch for 'smbstatus -L --resolve-uids' to show usernames
> > instead of UIDs as I have a customer request for it.
> > 
> > However Andrew rejected the patch to go in without a test. I've tried to
> > implement a test for smbstatus but it doesn't work. My problem is that I'm
> > not able to create a lock on a file to show up with smbstatus later.
> > 
> > I can:
> > 
> > open <file>
> > 
> > but I can't pass the returned fnum to
> > 
> > lock <fnum> r 0x0 0x1
> Looks like lock is obly implemented for SMB1. Also, you seem to use a
> hardcoded fnum value of 0, for SMB2+ I seem to get 1, and for SMB1 it's
> worse, as you'll get a random number there.

I just put 0 there to have a number, you need to pass the one you get from 
open which I can't. So with SMB2+ it would be more reliable, but we don't have 
Unix extensions yet (*hint*)!

> > to create a lock. See attached patch ...
> > 
> > Any suggestions how to move forward?
> Implement lock for SMB2?
> I personally wouldn't care about a test for smbstatus output, that's an
> untested mess anyway. If we have something like stable JSON output, then
> sure.

Push the 'smbstatus -L --resolve-uids' patch and I'm totally happy :-)

Best regards,


Andreas Schneider                      asn at
Samba Team                   
GPG-ID:     8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D

More information about the samba-technical mailing list