5,576
edits
Changes
From SME Server
Jump to navigationJump to searcha
* see informations of a user
* see informations of a user
id USER
id USER
====Manual Settings for specific Needs====
Nfs offers a lot of parameters and you may need some specific settings that it would be difficult or dangerous to let them in all hands. So for some cases you can enable by db command your nfs shares
but you cannot :
* use the wildcard '*'
* open your shares to ip(s) outside of your local network(s)
* use a domain to define your shares, the ip or the network are a mandatory
* use the root '/'
* let a space between the ip and its share definition
IF you want to do all these dangerous things, then you need to do them by custom templates.
How enable specific rules :
config setprop nfs-rules '''MYRULE''' '/home/e-smith/files/ibays/IBAYNAME/files 192.168.14.0/22(nohide,sync,wdelay,rw,no_root_squash,secure)'
or
config setprop nfs-rules '''MYRULE''' '/home/e-smith/files/ibays/IBAYNAME/files 192.168.14.154(nohide,sync,wdelay,rw,no_root_squash,secure)'
There is no analysis of the share settings, ditto for the path of the folder you want to share (except for the '/')
once modified
signal-event nfs-conf
==== Couple of notes whilst installing on SME9..... ====
==== Couple of notes whilst installing on SME9..... ====
