smb.conf/manpage/2006/parameters/O

from HTYP, the free directory anyone can edit if they can prove to me that they're not a spambot
< smb.conf‎ | manpage‎ | 2006‎ | parameters
Jump to: navigation, search

obey pam restrictions

      obey pam restrictions (G)
             When Samba 3.0 is configured to enable PAM support (i.e. --with-pam), this parameter will control whether or not Samba should obey PAM's account and session management directives. The default behavior is to use PAM for clear text authentication only and to ignore any account or session management. Note that Samba always ignores PAM for authentication in the case of _�e_�n_�c_�r_�y_�p_�t _�p_�a_�s_�s_�w_�o_�r_�d_�s _�= _�y_�e_�s. The reason is that PAM modules cannot support the challenge/response authentication mechanism needed in the presence of SMB password encryption.
             Default: _�o_�b_�e_�y _�p_�a_�m _�r_�e_�s_�t_�r_�i_�c_�t_�i_�o_�n_�s = no

only user

      only user (S)
             This is a boolean option that controls whether connections with usernames not in the _�u_�s_�e_�r list will be allowed. By default this option is disabled so that a client can supply a username to be used by the server. Enabling this parameter will force the server to only use the login names from the _�u_�s_�e_�r list and is only really useful in share level security.
             Note that this also means Samba won't try to deduce usernames from the service name. This can be annoying for the [homes] section. To get around this you could use u�us�se�er�r =�= %�%S�S which means your _�u_�s_�e_�r list will be just the service name, which for home directories is the name of the user.
             Default: _�o_�n_�l_�y _�u_�s_�e_�r = no

oplock break wait time

      oplock break wait time (G)
             This is a tuning parameter added due to bugs in both Windows 9x and WinNT. If Samba responds to a client too quickly when that client issues an SMB that can cause an oplock break request, then the network client can fail and not respond to the break request. This tuning parameter (which is set in milliseconds) is the amount of time Samba will wait before sending an oplock break request to such (broken) clients.


             W�Wa�ar�rn�ni�in�ng�g
             DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE.
      Default: _�o_�p_�l_�o_�c_�k _�b_�r_�e_�a_�k _�w_�a_�i_�t _�t_�i_�m_�e = 0

oplock contention limit

      oplock contention limit (S)
             This is a v�ve�er�ry�y advanceds�sm�mb�bd�d(8) tuning option to improve the efficiency of the granting of oplocks under multiple client contention for the same file.
             In brief it specifies a number, which causes s�sm�mb�bd�d(8)not to grant an oplock even when requested if the approximate number of clients contending for an oplock on the same file goes over this limit. This causes s�sm�mb�bd�d to behave in a similar way to Windows NT.


             W�Wa�ar�rn�ni�in�ng�g
             DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE.
      Default: _�o_�p_�l_�o_�c_�k _�c_�o_�n_�t_�e_�n_�t_�i_�o_�n _�l_�i_�m_�i_�t = 2

oplocks

      oplocks (S)
             This boolean option tells s�sm�mb�bd�d whether to issue oplocks (opportunistic locks) to file open requests on this share. The oplock code can dramatically (approx. 30% or more) improve the speed of access to files on Samba servers. It allows the clients to aggressively cache files locally and you may want to disable this option for unreliable network environments (it is turned on by default in Windows NT Servers). For more information see the file_�S_�p_�e_�e_�d_�._�t_�x_�t in the Samba _�d_�o_�c_�s_�/ directory.
             Oplocks may be selectively turned off on certain files with a share. See the  _�v_�e_�t_�o _�o_�p_�l_�o_�c_�k _�f_�i_�l_�e_�s parameter. On some systems oplocks are recognized by the underlying operating system. This allows data synchronization between all access to oplocked files, whether it be via Samba or NFS or a local UNIX process. See the_�k_�e_�r_�n_�e_�l _�o_�p_�l_�o_�c_�k_�s parameter for details.
             Default: _�o_�p_�l_�o_�c_�k_�s = yes

os2 driver map

      os2 driver map (G)
             The parameter is used to define the absolute path to a file containing a mapping of Windows NT printer driver names to OS/2 printer driver names. The format is:
             <nt driver name> = <os2 driver name>.<device name>
             For example, a valid entry using the HP LaserJet 5 printer driver would appear as H�HP�P L�La�as�se�er�rJ�Je�et�t 5�5L�L =�= L�LA�AS�SE�ER�RJ�JE�ET�T.�.H�HP�P L�La�as�se�er�rJ�Je�et�t 5�5L�L.
             The need for the file is due to the printer driver namespace problem described in ???. For more details on OS/2 clients, please refer to ???.
             Default: _�o_�s_�2 _�d_�r_�i_�v_�e_�r _�m_�a_�p =

os level

      os level (G)
             This integer value controls what level Samba advertises itself as for browse elections. The value of this parameter determines whether n�nm�mb�bd�d(8) has a chance of becoming a local master browser for the  _�W_�O_�R_�K_�G_�R_�O_�U_�P in the local broadcast area.
             N�No�ot�te�e :�:By default, Samba will win a local master browsing election over all Microsoft operating systems except a Windows NT 4.0/2000 Domain Controller. This means that a misconfigured Samba host can effectively isolate a subnet for browsing purposes. See _�B_�R_�O_�W_�S_�I_�N_�G_�._�t_�x_�t  in the Samba _�d_�o_�c_�s_�/ directory for details.
             Default: _�o_�s _�l_�e_�v_�e_�l = 20
             Example: _�o_�s _�l_�e_�v_�e_�l = 65