Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

10.4: Avoid a 10.3/10.4 file sharing bug Network
Tiger only hintHere's a workaround for a somewhat obscure file sharing bug. If you have an external drive on a Panther machine you are sharing, do NOT check the Ignore Ownership box in the Get Info window. If you do, there is a bug in the Tiger client such that it can no longer write to that drive -- reading is fine.

I called Apple's tech support and was able to get their tech to reproduce the problem. He seemed quite surprised that this was such a simple bug to reproduce. I have not confirmed if this problem occurs when sharing drives between Tiger and Tiger.

I turned this checkbox on as I have a very simple network and want people to read/write anywhere on this drive and not get ownership headaches. Unix in a nice OS, but its file permissions, while very powerful, are not well suited for a home network where security is a very low priority.

[robg adds: I can't confirm this one, as I no longer have a Panther machine available. But it's apparently been verified by Apple, so hopefully, a fix is coming soon...]
    •    
  • Currently 4.00 / 5
  You rated: 5 / 5 (4 votes cast)
 
[7,691 views]  

10.4: Avoid a 10.3/10.4 file sharing bug | 3 comments | Create New Account
Click here to return to the '10.4: Avoid a 10.3/10.4 file sharing bug' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.4: Avoid a 10.3/10.4 file sharing bug
Authored by: david-bo on Jun 01, '05 12:07:18PM

I can confirm that this bug also occurs in a 10.3 - 10.3 environment.

---
http://www.google.com/search?as_q=%22Authored+by%3A+david-bo%22&num=10&hl=en&ie=ISO-8859-1&btnG=



[ Reply to This | # ]
10.4: Avoid a 10.3/10.4 file sharing bug
Authored by: giaguara on Jun 01, '05 05:23:37PM

I can't reproduce it with 10.3 and 10.4... or, initially had some "can't write" problem -- those were simply corrected by reselecting the "ignore ownership of volume" from 10.4 side, as it did not appear to have transferred correctly from 10.3. -- 10.3.5 Server, and 10.4 Server, but as the base system is the same with client and Server, should be the same.
I had never figured out this could be seen as a problem.

---
Giaguara



[ Reply to This | # ]
Work-around for bug:
Authored by: wibbble on Jun 08, '05 12:20:03AM

I've also run into this highly annoying bug. One work-around I've found is to log into the 10.3 file server as the currently logged-in user.

When I do that, I can write to the external drives as normal.



[ Reply to This | # ]