Just found out this little tidbit... hopefully it can prevent some hair loss...
I have an account for myself and my wife on my MBP. I have my iTunes sitting on my TimeCapsule which both accounts were pointing to for access to the library. Under 10.5 I was able to have both accounts logged in and accessing the TC library and TC in general at the same time (ie. have iTunes up and running on both accounts).
Now that I upgraded to 10.6 only one account can actually see the TimeCapsule and browse within it. The other account can see the TimeCapsule but gets access denied when trying to browse into it.
At the system level the permissions are set to drwx------ and cannot be changed even by root.
When I called AppCare they seemed surprised that this ever worked. And funny thing is that I have a Buffalo NAS as well that works the way it is supposed to and both accounts can see it at the same time and browse it as well. Looks like I need to move my library and music yet again
I am still waiting to hear back from them as to whether they consider this a bug or enhancement request. I will post back when I get an answer
I have an account for myself and my wife on my MBP. I have my iTunes sitting on my TimeCapsule which both accounts were pointing to for access to the library. Under 10.5 I was able to have both accounts logged in and accessing the TC library and TC in general at the same time (ie. have iTunes up and running on both accounts).
Now that I upgraded to 10.6 only one account can actually see the TimeCapsule and browse within it. The other account can see the TimeCapsule but gets access denied when trying to browse into it.
At the system level the permissions are set to drwx------ and cannot be changed even by root.
When I called AppCare they seemed surprised that this ever worked. And funny thing is that I have a Buffalo NAS as well that works the way it is supposed to and both accounts can see it at the same time and browse it as well. Looks like I need to move my library and music yet again
I am still waiting to hear back from them as to whether they consider this a bug or enhancement request. I will post back when I get an answer