Difference between revisions of "smb.conf/manpage/2006/parameters/K"
< smb.conf | manpage | 2006 | parameters
Jump to navigation
Jump to search
(splitting into subpages) |
(No difference)
|
Latest revision as of 14:55, 5 September 2010
keepalive
keepalive (G)
The value of the parameter (an integer) represents the number of
seconds between _�k_�e_�e_�p_�a_�l_�i_�v_�e packets. If this parameter is zero, no
keepalive packets will be sent. Keepalive packets, if sent,
allow the server to tell whether a client is still present and
responding.
Keepalives should, in general, not be needed if the socket being
used has the SO_KEEPALIVE attribute set on it (see _�s_�o_�c_�k_�e_�t
_�o_�p_�t_�i_�o_�n_�s). Basically you should only use this option if you
strike difficulties.
Default: _�k_�e_�e_�p_�a_�l_�i_�v_�e = 300
Example: _�k_�e_�e_�p_�a_�l_�i_�v_�e = 600
kernel change notify
kernel change notify (G)
This parameter specifies whether Samba should ask the kernel for
change notifications in directories so that SMB clients can
refresh whenever the data on the server changes.
This parameter is only used when your kernel supports change
notification to user programs, using the F_NOTIFY fcntl.
Default: _�k_�e_�r_�n_�e_�l _�c_�h_�a_�n_�g_�e _�n_�o_�t_�i_�f_�y = yes
kernel oplocks
kernel oplocks (G)
For UNIXes that support kernel based _�o_�p_�l_�o_�c_�k_�s (currently only
IRIX and the Linux 2.4 kernel), this parameter allows the use of
them to be turned on or off.
Kernel oplocks support allows Samba _�o_�p_�l_�o_�c_�k_�s to be broken when-
ever a local UNIX process or NFS operation accesses a file that
s�sm�mb�bd�d(8) has oplocked. This allows complete data consistency
between SMB/CIFS, NFS and local file access (and is a v�ve�er�ry�y cool
feature :-).
This parameter defaults to o�on�n, but is translated to a no-op on
systems that no not have the necessary kernel support. You
should never need to touch this parameter.
Default: _�k_�e_�r_�n_�e_�l _�o_�p_�l_�o_�c_�k_�s = yes