Currently Being ModeratedMar 6, 2013 10:00 PM (in response to bonin)
Why does the MPI user need to have a network home directory? That would be inefficient, even if it worked.
Currently Being ModeratedMar 6, 2013 10:43 PM (in response to Linc Davis)
I hooked a Thunderbolt-Ethernet adapter to Mac mini. Each Mac mini can have two network interfaces; one for file sharing and the other for MPI communication. So a network home directory would not interfere MPI communication. I have not yet connected Mac minis to the second switch for a dedicated network for MPI communication. The user can change configuration once on the iMac and it is available on every Mac mini with a network home directory.
Currently Being ModeratedMar 6, 2013 11:02 PM (in response to bonin)
I doubt this is the best way to do things, but you may have better luck with NFS home directories. You can't set that up with Server.app.
Currently Being ModeratedMar 7, 2013 1:57 AM (in response to bonin)
I don't think having SSH keys has any effect at all over AFP authentication. Two seperate authentication mechanisms at work here.
For SSH keys to work, each user ID on our local machines would need a matching network user defined on the server, and the authorized keys stored in that user's ~/.ssh folder on the server.
Once you get SSH working, you can use scp and rsync to move files around.
Currently Being ModeratedMar 7, 2013 12:48 PM (in response to Linc Davis)
I have no problem with SSH remote login to a home shared with AFP. Just public key authentication is unstable (work not always). I have authorized_keys in ~/.ssh with a correct permission.
Considering that AFP is a technology from classic Mac OS, SSH may not work well with AFP. NFS should work better with SSH. I'll try NFS.