On Mon, Feb 02, 2004 at 02:12:16PM -0600, Thomas Hannan wrote: > This is exactly the case -- I want it to NOT pass down a 64 bit lock to > fcntl but it does. I unfortunately have no alternative but to re-export > an NFS mount (v3 on linux), and have tried to make it fail the configure > test for 64 bit fcntl, but have not succeeded. (in the configure script, > I simply made either result of the conftest for 64 bit fcntl locking set > samba_cv_HAVE_STRUCT_FLOCK64=no) ... > > even when I compile after telling it that I don't have 64bit locking, i > still get loads of errors in my syslog from smbd > locking/posix.c:posix_fcntl_lock(656) an No locks available error. This > can happen when using 64 bit offsets .... > > I wish I could find a way to not have to re-export an NFS mount, but > there's no way around it and I know that when I tested with an old 2.2 > binary that it worked beautifully, but I wasn't able to use any of the > new features in 3.0, or test out new RC versions...
You could try doing the configure in the NFS mounted directory. I think configure runs the tests in the current directory. Then the 64-bit locking tests should fail and Samba should set itself up as only supporting 32-bit signed locks. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
