Software: Apache/2.0.54 (Fedora). PHP/5.0.4 uname -a: Linux mina-info.me 2.6.17-1.2142_FC4smp #1 SMP Tue Jul 11 22:57:02 EDT 2006 i686 uid=48(apache) gid=48(apache) groups=48(apache) Safe-mode: OFF (not secure) /usr/bin/X11/./../../share/doc/nfs-utils-1.0.7/ drwxr-xr-x |
Viewing file: Select action/file-type: ![]() ![]() ![]() Next: Performance Up: Interoperability Previous: Other Considerations ResultsWe performed our tests on the Linux NFS server under Linux 2.2.9 plus kernel patches from knfsd 1.4.2, which contains all the necessary changes to ensure interoperability with other NFS implementations. We ran the Connectathon testsuites on Solaris 7/Sparc client, Solaris 7/x86 client and Linux client. The Solaris test results are in Appendix A. They showed that the Linux kernel-space NFS server passed all the tests serving Solaris clients. In the Linux test result in Appendix B, there is a warning:
Test #13 - Check locking and mmap semantics. Parent: 13.0 - F_TLOCK [ ffe, ENDING] PASSED. Parent: 13.1 - mmap [ 0, 1000] WARNING! Parent: **** Expected EAGAIN, returned success... From the comment in the test:
/* * Can a file be locked and mapped at same time? It's * potentially safe if the whole file is locked, or if the * locked region is page-aligned. Otherwise, there is a * race condition between two clients that lock disjoint * regions of the same page. So for this test we * deliberately lock a region that is not * page-aligned--that should cause the mmap to fail. But if * it doesn't, that's arguably not an interoperability * problem, so make it a warning, not a fatal error. */ This warning is due to the Linux NFS client implementation. It doesn't affect the interoperability of the Linux NFS server.
H.J. Lu 1999-08-15 |
:: Command execute :: | |
--[ c99shell v. 1.0 pre-release build #16 powered by Captain Crunch Security Team | http://ccteam.ru | Generation time: 0.0031 ]-- |