Could anyone on the list please confirm or deny if they see this bug?
Off list is fine, and I may ask a few follow up questions.
I've had several people confirm it, but no one deny it with these
specific server settings.
Server:
Xserve RAID connected via FC to Xserve running 10.3.9, sharing 2
folders via AFP on the RAID called test1 and test2
Client:
OS X 10.3.9-10.4.2
Bug:
Mount both test1 and test2 on the client. Can you add both
sharepoints to the dock? In my system, the first sharepoint moves to
where you tried to place the second sharepoint.
Caveats:
-RAID is actually being mounted with Xsan via FC switch though others
have have confirmed this bug without Xsan or FC switch in the
picture.
-Bug exhibits when any of the following AFP server settings are tried
Guest on/off, secure connections on/off, authenticate any method,
Rendezvous&Appletalk on/off, logging on/off, idle users
sleep/disconnect/except on any option.
The backing store for the sharepoint should make no difference. The
issue is on your clients, not the server.
Since having sharepoints in the dock works fine, I'd start looking at
the user and or machine(s) in question, how their HOMEs are
implemented, et cetera.
I'd start with a freshly installed OS X client and try this on a test
machine.
--
-dhan
Clean installs of 10.3.9, 10.4.2, 10.4.2 Server all exhibit this
symptom on my LAN.
Users are all local users with local home dirs. Nothing special,
especially with clean installs.
The backing store may be the problem as Xsan may not be providing a
device name that the Finder is happy with. At least according to an
Apple SE who has recreated the problem.
More symptoms of the bug:
1. Mount 3 share points, move them all to the dock at once works fine.
Move them one at a time and only the first one stays in the dock.
2. No bug if sharepoints are mounted via SMB instead of AFP.
3. I actually have 4 servers as part of my Xsan setup (2 MDCs, 2 file
servers). The symptoms occur if I try to mount from any of the
servers.
Point 2 leads me to believe it's an AFP filesystem problem. Just not
sure if it's on the server or client side, especially if it's a bug in
the client FS on how it handles Xsan volumes.
Stu Duncan
IS Manager
Cox North Carolina Publications, Inc.
(252) 329-9628
email@hidden
http://www.reflector.com
