Difference between revisions of "NFS"
Line 48: | Line 48: | ||
signal-event post-upgrade; signal-event reboot | signal-event post-upgrade; signal-event reboot | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== Couple of notes whilst installing on SME8..... == | == Couple of notes whilst installing on SME8..... == | ||
Line 131: | Line 116: | ||
However, I don't think this starts/restarts rpcbind, hence the reboot on install which should not really be necessary. | However, I don't think this starts/restarts rpcbind, hence the reboot on install which should not really be necessary. | ||
+ | ==see exported folders== | ||
+ | You can have a look on all exported folders and see for which ip/network they are allowed. | ||
+ | # showmount -e | ||
+ | Export list for hpcompact: | ||
+ | /home/e-smith/files/ibays/toto/files 192.168.15.0/24,192.168.12.0/24 | ||
+ | /home/e-smith/files/ibays/laurence/files 192.168.12.100,192.168.12.125 | ||
+ | /home/e-smith/files/ibays/dolibarr/files 192.168.15.0/24,192.168.12.0/24 | ||
+ | /home/e-smith/files/ibays/admin_25465/files 192.168.15.0/24,192.168.12.0/24 | ||
+ | |||
+ | |||
+ | ==find connected clients== | ||
+ | netstat -an | grep nfs.server.ip:port | ||
+ | * for example | ||
+ | # netstat -an | grep 192.168.12.125:2049 | ||
+ | tcp 0 0 192.168.12.125:2049 192.168.12.25:850 ESTABLISHED | ||
==client side== | ==client side== |
Revision as of 00:10, 7 December 2014
How To use SME as an NFS server
This came from a dtech post about to use SME as a NFS server
1. Install the smeserver-nfs contrib like this:
yum install smeserver-nfs --enablerepo=smecontribs
2. Then execute the following:
- sme8
config setprop nfs status enabled config setprop portmap status enabled config setprop nfslock status enabled
- sme9
config setprop nfs status enabled config setprop rpcbind status enabled config setprop nfslock status enabled
3. Edit /etc/exports to add the directories to be shared (this line exports user home directories and ibays):
/home/e-smith/files *.mydomain(rw,sync,no_wdelay,nohide,no_root_squash)
/home/e-smith/files – shared directory 192.168.1.0/24 – IP address range of clients or *.mydomain – Domain's client allowed rw – Writable permission to shared folder sync – Synchronize shared directory no_root_squash – Enable root privilege no_all_squash – Enable user’s authority
if you want to see all your exports
showmount -e
4. Then, the following, which will reboot the server:
signal-event post-upgrade; signal-event reboot
Couple of notes whilst installing on SME8.....
DB options as follows - status disabled by default :
nfs=service TCPPorts=2049,4002,4003 UDPPorts=2049,4002,4003 access=private mountdPort=4002 rquotadPort=4003 status=disabled
nfslock=service TCPPorts=4000,4001,4004 UDPPorts=4000,4001,4004 access=private lockdPort=4001 statdOutgoingPort=4004 statdPort=4000 status=disabled
portmap=service TCPPort=111 UDPPort=111 access=private status=disabled
After installation & reboot you should be able to update with
signal-event remoteaccess-update
However, I don't think this starts/restarts portmap, hence the reboot on install which should not really be necessary.
Couple of notes whilst installing on SME9.....
DB options as follows - status disabled by default :
nfs=service TCPPorts=2049,4002,4003 UDPPorts=2049,4002,4003 access=private mountdPort=4002 rquotadPort=4003 status=disabled
nfslock=service TCPPorts=4000,4001,4004 UDPPorts=4000,4001,4004 access=private lockdPort=4001 statdOutgoingPort=4004 statdPort=4000 status=disabled
rpcbind=service TCPPort=111 UDPPort=111 access=private status=disabled
After installation & reboot you should be able to update with
signal-event remoteaccess-update
However, I don't think this starts/restarts rpcbind, hence the reboot on install which should not really be necessary.
see exported folders
You can have a look on all exported folders and see for which ip/network they are allowed.
# showmount -e Export list for hpcompact: /home/e-smith/files/ibays/toto/files 192.168.15.0/24,192.168.12.0/24 /home/e-smith/files/ibays/laurence/files 192.168.12.100,192.168.12.125 /home/e-smith/files/ibays/dolibarr/files 192.168.15.0/24,192.168.12.0/24 /home/e-smith/files/ibays/admin_25465/files 192.168.15.0/24,192.168.12.0/24
find connected clients
netstat -an | grep nfs.server.ip:port
- for example
# netstat -an | grep 192.168.12.125:2049 tcp 0 0 192.168.12.125:2049 192.168.12.25:850 ESTABLISHED
client side
- nfs-comon
install nfs-common (it depends of your distribution)
- mount the network share
mkdir /mnt/partage mount -t nfs 192.168.xx.xxx:/home/e-smith/files /mnt/partage ll /mnt/partage
ToDos
Probably better to make a custom template for /etc/exports
Would be better if there was a web panel to enable/disable nfs per ibay