|
|
#1 |
|
Registered User
Join Date: Jun 2005
Posts: 1
|
In 10.3 I was happily serving up my main file repository to my Debian-woody Apache/2 web server over NFS. This was using the standard NFS Export through the Workgroup Manager on the Tiger server. On the Debian web server, I was able to view directory listings of the NFS output and the files (through mod_autoindex -- the default).
I Upgraded to 10.4 and had a startling issue. It seems that readdir()s have stopped working on the Debian machine. The web server's listings would show no directories in its output. However, I could still get to files if I typed in their absolute path in my browser; I could even get more empty directory listings if I typed in the path to a known directory, as opposed to a 404. Having a hunch on the readdir() problem, I made this command line script for PHP to test it out: PHP Code:
php -f /tmp/x.php dir opened fine . .. I'm also experiencing the same problem on a brand new install of Gentoo, even off the install CD. I've tried calling Applecare, but they claim ignorance on the issue, and offered assistance for $699 for escalation with a third party product. I've been unable to find any other cases like this on google, besides a mention that 10.4.2 is bringing enhancements to NFS. I don't think this is related to the client side of things, as the problem only started immediately after upgrading from 10.3.9 to 10.4.1. Does anyone have any information, links, configuration settings, etc, to help out with this problem? |
|
|
|
|
|
#2 |
|
Registered User
Join Date: Mar 2007
Posts: 1
|
I found this [ http://docs.info.apple.com/article.html?artnum=303696 ]
which says Mac OS X Server 10.4: Third-party clients cannot see contents of NFS export HFS Plus file systems exported by Mac OS 10.4 and later use 64-bit values in the NFSv3 READDIR cookies. Some clients running non-Apple operating systems may only be able to handle 32-bit values in the NFSv3 64-bit READDIR cookies. These clients will not see the full contents of NFS shares exported by a Mac OS X 10.4 Server. To resolve the issue, use one of these two solutions: * Export the NFS directory using the "-32bitclients" option. Note: This requires Mac OS X Server 10.4.3 or later. -- Or -- * Have the client OS access the share using NFSv2 (which only has 32-bit READDIR cookies) instead of NFSv3. |
|
|
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|