Finder
'Go' Menu
'Connect to server'
nfs://server/share
How the hell hard is that?!
Discussion on:
View:
Show:
What are you connecting to? Over here, connecting to Linux servers, it is not nearly this easy. I wish it were. Using Finder like this does not allow you to set the mount options that seem to make all the difference.
If you are using some other protocol than AFP, then you need to specify it.
When you just type in the address/IP of the server, the connect to dialog ASSUMES the AFP protocol.
However, if you put 'nfs://' or 'smb://', that should give you the shares after specifying your login details.
Say the server's IP is 172.0.0.10.
Go>Connect to Server...
The put in "smb://172.0.0.10"
Then it asks for the login details, and will then give you the list of shares you have access to just like normal with an AFP (Apple Filing Protocol) server.
Any linux server that hosts machines other than linux workstations SHOULD have SMB enabled, and Macs can connect to those shares.
Sorry for the late response!
When you just type in the address/IP of the server, the connect to dialog ASSUMES the AFP protocol.
However, if you put 'nfs://' or 'smb://', that should give you the shares after specifying your login details.
Say the server's IP is 172.0.0.10.
Go>Connect to Server...
The put in "smb://172.0.0.10"
Then it asks for the login details, and will then give you the list of shares you have access to just like normal with an AFP (Apple Filing Protocol) server.
Any linux server that hosts machines other than linux workstations SHOULD have SMB enabled, and Macs can connect to those shares.
Sorry for the late response!
When you say "rsize=3276" do mean "rsize=32768" ???
If so, could we then just say "rwsize=32768"
Could you please give some reasoning behind upping this from the default?
If so, could we then just say "rwsize=32768"
Could you please give some reasoning behind upping this from the default?
"intr" is typically not relevant with "soft". "soft" means that an unresponsive server causes an error on the client, which may cause problems with memory-mapped I/O (including executables) or with programs that don't bother to check for I/O errors. The opposite of "soft" is "hard", which means the client keeps trying until the server comes back up. Together with "hard", "intr" means that it's possible to kill a program that's waiting for the server to respond.
Since "soft" can cause data loss, and cause processes running NFS mounted executables to die if the server becomes unresponsive, "hard,intr" is almost always a better choice.
If you nevertheless have some reason to favor "soft" mounts, I'd be interested in hearing it.
Since "soft" can cause data loss, and cause processes running NFS mounted executables to die if the server becomes unresponsive, "hard,intr" is almost always a better choice.
If you nevertheless have some reason to favor "soft" mounts, I'd be interested in hearing it.
Any way to set this up from the command line? The benefits of doing it that way are obvious to anyone who administers more than one machine. And even for one machine it's a lot easier to document and repeat (if necessary) what you did.
Hi, this is a great article but can you provide a little more info about what you meant by
"The key is the advanced mount options; without those options, setting up OS X as an NFS client will be more painful than it needs to be."
I know I can read the man page to get lots of specifics, just looking for a high level overview of what "pains" you were referring to.
Also, do you know if there is a way to create drive shortcuts for mounted NFS drives in OSX?
Thanks
Alex
"The key is the advanced mount options; without those options, setting up OS X as an NFS client will be more painful than it needs to be."
I know I can read the man page to get lots of specifics, just looking for a high level overview of what "pains" you were referring to.
Also, do you know if there is a way to create drive shortcuts for mounted NFS drives in OSX?
Thanks
Alex
i am trying this with openindiana. the max speed i get is ~20mb/sec... any idea how to increase this? i am on a gigabit ethernet network.
Hi all,
I'm looking for a solution regarding the refresh problem on Lion OS with the nfs volumes.
I am configuring a system with a GBLabs NAS and 3 Mac clients, Lion and Snow Leopard, and everything is working correctly with the Leopard but the Lions are not refreshing the information when renaming files or folders.
Do you know if this is being fixed with Mountain Lion or any other way to solve it?
Best regards,
Csar
I'm looking for a solution regarding the refresh problem on Lion OS with the nfs volumes.
I am configuring a system with a GBLabs NAS and 3 Mac clients, Lion and Snow Leopard, and everything is working correctly with the Leopard but the Lions are not refreshing the information when renaming files or folders.
Do you know if this is being fixed with Mountain Lion or any other way to solve it?
Best regards,
Csar
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
