diff options
Diffstat (limited to 'docs/smbdotconf/tuning')
| -rw-r--r-- | docs/smbdotconf/tuning/getwdcache.xml | 3 | ||||
| -rw-r--r-- | docs/smbdotconf/tuning/keepalive.xml | 3 | ||||
| -rw-r--r-- | docs/smbdotconf/tuning/maxconnections.xml | 3 |
3 files changed, 3 insertions, 6 deletions
diff --git a/docs/smbdotconf/tuning/getwdcache.xml b/docs/smbdotconf/tuning/getwdcache.xml index cac8dba47b..74d30c28e5 100644 --- a/docs/smbdotconf/tuning/getwdcache.xml +++ b/docs/smbdotconf/tuning/getwdcache.xml @@ -6,8 +6,7 @@ <para>This is a tuning option. When this is enabled a caching algorithm will be used to reduce the time taken for getwd() calls. This can have a significant impact on performance, especially - when the <link linkend="WIDELINKS"><parameter moreinfo="none">wide links</parameter> -</link> parameter is set to <constant>no</constant>.</para> + when the <smbconfoption name="wide smbconfoptions"/> parameter is set to <constant>no</constant>.</para> </description> <value type="default">yes</value> diff --git a/docs/smbdotconf/tuning/keepalive.xml b/docs/smbdotconf/tuning/keepalive.xml index 5648253478..0586365512 100644 --- a/docs/smbdotconf/tuning/keepalive.xml +++ b/docs/smbdotconf/tuning/keepalive.xml @@ -11,8 +11,7 @@ a client is still present and responding.</para> <para>Keepalives should, in general, not be needed if the socket - has the SO_KEEPALIVE attribute set on it by default. (see <link linkend="SOCKETOPTIONS"> - <parameter moreinfo="none">socket options</parameter></link>). + has the SO_KEEPALIVE attribute set on it by default. (see <smbconfoption name="socket options"/>). Basically you should only use this option if you strike difficulties.</para> </description> diff --git a/docs/smbdotconf/tuning/maxconnections.xml b/docs/smbdotconf/tuning/maxconnections.xml index ac014100ea..1e3043b2f7 100644 --- a/docs/smbdotconf/tuning/maxconnections.xml +++ b/docs/smbdotconf/tuning/maxconnections.xml @@ -9,8 +9,7 @@ of zero mean an unlimited number of connections may be made.</para> <para>Record lock files are used to implement this feature. The lock files will be stored in - the directory specified by the <link linkend="LOCKDIRECTORY"> - <parameter moreinfo="none">lock directory</parameter></link> option.</para> + the directory specified by the <smbconfoption name="lock directory"/> option.</para> </description> <value type="default">0</value> |