smbstatus fails with "Segmentation fault"

[David Collier-Brown]

Arnold Troeger wrote:
> The thing is, samba mostly works with large file support (without having
> tried to read a large file that is).  The particular routine that choked
> deals with share locking.  The SIGBUS error occurs when smbstatus scans
> for share locks in the shm_share_forall procedure.  Specifically, the
> program tries to get the pid of the locking process in
> "entry_scanner_p->e.pid".

> >         Those warnings are the tip-off: we need to hunt down the
> >         erroneous shifts and repair them.
> 
> I agree.  This is a problem that should be fixed.  I need to know more
> about how the share locking works in order to be able to identify the
> problem though.  I have the source code but if someone could describe the
> algorithm for me, I would very much appreciate it.

	Alas, I don't: one of the real gurus will need to comment.

	My leaky memory say locking (actually lock-address-folding)
	has been worked on lately: I wonder if this is a new
	problem that only shows up on Slolaris?

--dave
-- 
David Collier-Brown,  | Always do right. This will gratify some people
185 Ellerslie Ave.,   | and astonish the rest.        -- Mark Twain
Willowdale, Ontario   | //www.oreilly.com/catalog/samba/author.html
Work: (905) 415-2849 Home: (416) 223-8968 Email: davecb at canada.sun.com