I just updated from 3.4.5 to 3.4.7 and now my symlinks are not followed when connected via Mac Leopard. Leopard currently has a known issue where it doesn't follow the symlinks correctly, but this issue is resolved by setting unix extensions = no. However, with the latest update to 3.4.7, the symlink folders show up as folders but they are empty when opened on the Leopard system, and the appear as files that disappear when clicked on. This is obviously something that broke with the 3.4.7 release.
Can you attach a wireshark trace and a debug level 10 log to this bug please so we can investigate ?
I've not used wireshark, I usually use tcpdump, but from what I can tell the log format is the same - I'm attaching the output of the following tcpdump command:
tcpdump -s 65535 -w /tmp/samba_dump host 192.168.7.12
as well as the corresponding log level 10. The commands executed while logging:
9:07:15 - connect
9:07:25 - open the symlink folder
9:07:40 - disconnect
Created attachment 5488 [details]
Log Level 10 output
Created attachment 5489 [details]
tcpdump output mentioned above
Can you give me a ls -lR of the symlink folder, so I know what the symlinks are in the wireshark trace please ?
Uploaded the output of ls -lR to
(the file was too large to attach, there's a lot of files there)
As a follow up, I just received an issue with a Windows user experiencing a similar problem with a symbolic link in their homes folder, so this is not specific to Macs. They had been able to access the folder without issue, then suddenly it was not allowing them to. (I was not at the computer in question and was merely trying to get them back as quickly as possible so I have no further details). I was able to get them to be able to work correctly by moving the linked folder and then putting a symlink where it was originally, which worked in this case because the original location was for apache which is following the new symlink just fine, but I do have some symlinks where multiple users need access, so I'm bracing myself for when this comes up. At this point it looks like I may need to roll back to an older version of samba unless a fix is pending.
I didn't see this anymore with OS X 10.6 and Samba 3.6. Can you confirm that this is no issue any more?