[Samba] Problems with 2.2.3

[Al Smith]

Dear Samba team,

I upgraded to 2.2.3 on Feb 4th; everything seemed to be in order, however
today I have noticed some severe problems which have been resolved only be
moving back to 2.2.2.

I have a [print$] share, and it has been observed by the users that if
they remove all their printers then their system functions as normal.
Adding one (or more) printers and then starting an application such as
Office (any of Word, Excel, etc) or Netscape is incredibly slow.

I would surmise (although I have no firm evidence for this) that the
slowness is caused by the application keeping its eye on the default
printer queue.

smbstatus reports in 2.2.3 that many users seem to be attempting to create
locks on the files within the [print$]/W32X86/2 directory where the
printer driver files are kept; for example:

3487321 DENY_WRITE RDONLY NONE
/sys/inet/samba/printers/W32X86/2/hp4050_6.ppd Thu Feb 7 14:47:02 2002

This locking is not observed in 2.2.2.

In the log.smbd, many error messages occur to do with locking files in the
[print$] share, for example:

[2002/02/07 14:38:59, 0] smbd/open.c:(551)
  open_mode_check: exlusive oplock left by process 3344765 after break !
For file W32X86/2/HPDCMON.DLL, dev = 1d0, inode = 6384365. Deleting it to
continue...
[2002/02/07 14:39:02, 0] smbd/oplock.c:(360)
  process_local_message: Received unsolicited break reply - dumping info.
[2002/02/07 14:41:51, 0] smbd/oplock.c:(758)
  oplock_break: receive_smb error (Error 0)
  oplock_break failed for file W32X86/2/pscript.sep (dev = 1d0, inode =
6384399, file_id = 1512).

I have no lines in my smb.conf which deal with oplocks, with the exception
of "locking = no" in the [netlogon] share.

We have for [print$]:

[print$]
path = /sys/inet/samba/printers
guest ok = yes
browseable = yes
read only = yes
write list = @ntadmin

Removing the files in W32X86/2, removing ntdrivers.tdb, printing.tdb and
ntprinters.tdb and reinstalling the drivers onto the [print$] share using
an NT4 machine logged in as DOMAIN\root did not cure the problems. I have
regressed to 2.2.2 and now everything is working just fine.

I did not try entering "locking = no" into the [print$] share - would this
now be recommended for 2.2.3 and above?

The OS in question is IRIX 6.5.14m; samba was compiled with ./configure
--prefix=blahblah --with-quotas --with-utmp;make;make install.

Thanks for your comments,

Al.