printing, locking, etc in 2.2.0

[Jeremy Allison]

David Lee wrote:
> 
> When I first installed 2.2.0, we seemed to get bitten by a bug (quotas
> over NFS), since fixed, that caused smbd to SEGV and vanish.  But it left
> behind some apparently locked files, and subsequent attempts by the user
> (on a new smbd, of course) to access their files failed.  It seemed unable
> to break the lock despite (or because of?) the original process having
> gone.
> 
> OK, that particular quota bug has since been fixed.  But the example
> suggests a residual problem with unbreakable locks when an smbd has
> vanished into a "shouldn't happen" hole...

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.

Jeremy.

-- 
--------------------------------------------------------
Buying an operating system without source is like buying
a self-assembly Space Shuttle with no instructions.
--------------------------------------------------------