Okay, I removed the 'hold' flag on the needed packages and upgraded (again) and can confirm that it DOES work now - at least at first appearance. I'll be doing some stuff on the server tonight and will keep you apprised of any problems.
In the duplicate bug I saw someone implied that the remedy you gave is simply a workaround, not a fix, that it hides the issue, but doesn't solve it. With the flag set to "yes" if a symlink redirects to a share should not be accessible to that user will they be granted access? Of course this is provided that you're using samba permissions - not system ones. Also when the bug is fixed in the next (hopefully) upgrade will I/should I need to reset the symlink flag to "no"? Especially provided the symlink bypasses the samba permissions. Another thing I noted in my syslog was this line: "Mar 27 16:55:17 threeve smbd[25609]: can't open username map /etc/samba/smbusers. Error No such file or directory" Upon me trying to locate of "smbusers" I'm give no results. Is the smbusers file a thing of the past now? Sorry for all the questions, just trying to get a better grasp of what's going on. Thanks for all your help grant -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676029 Title: After upgrade, ALL of Samba's shares appear empty on OS X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1676029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
