[debian-users:31789] Re: SAMBA EXCEL File Error

[Taketoshi Sano <kgh12351@xxxxxxxxxxx>]

���쁗�l���ł��B

In <3C6B9001.2050201@xxxxxxxxx>,
  on "Thu, 14 Feb 2002 19:21:42 +0900',
   with "[debian-users:31786] Re: SAMBA EXCEL File Error",
 Tomoo Nomura <nomurat@xxxxxxxxx> ���� wrote:

> >   oplock = no
> >
> > �ɂ���΁A�p�t�H�[�}���X�͑��������܂����A���̃G���[�͂łȂ��Ȃ锤�ł��B
> 
> ����́A�ǂ��ł���̂ł��傤���H�@source����Ă��āArecompile�ł��傤���H

man 5 smb.conf ����ƁA�ȉ��̂悤�ȋL�q�����‚���܂��ˁB

       kernel oplocks (G)

              For  UNIXs  that support kernel based oplocks (cur-
              rently only  IRIX  but  hopefully  also  Linux  and
              FreeBSD soon) this parameter allows the use of them
              to be turned on or off.

              Kernel oplocks support allows Samba oplocks  to  be
              broken  whenever a local UNIX process or NFS opera-
              tion accesses a file that smbd has  oplocked.  This
              allows  complete data consistency between SMB/CIFS,
              NFS and local file access (and is a very cool  fea-
              ture :-).

              This  parameter  defaults  to  "On" on systems that
              have the support, and "off" on systems that  don�t.
              You should never need to touch this parameter.

              See also the "oplocks" and "level2 oplocks" parame-
              ters.


       level2 oplocks (S)

              This  parameter  (new  in  Samba  2.0.5)   controls
              whether  Samba  supports level2 (read-only) oplocks
              on a share. In Samba 2.0.5 this parameter  defaults
              to  "False" as the code is new, but will default to
              "True" in a later release.

              Level2,  or  read-only  oplocks  allow  Windows  NT
              clients  that have an oplock on a file to downgrade
              from a read-write oplock to a read-only oplock once
              a  second client opens the file (instead of releas-
              ing all oplocks on a  second  open,  as  in  tradi-
              tional, exclusive oplocks). This allows all openers
              of the file that support level2  oplocks  to  cache
              the  file  for  read-ahead  only  (ie. they may not
              cache writes or lock requests) and  increases  per-
              formance  for  many  acesses  of files that are not
              commonly written (such as application .EXE  files).

              Once  one  of  the  clients  which have a read-only
              oplock writes to the file all clients are  notified
              (no  reply  is  needed  or  waited for) and told to
              break their oplocks to "none" and delete any  read-
              ahead caches.

              It  is recommended that this parameter be turned on
              to speed access to shared executables (and also  to
              test the code :-).

              For more discussions on level2 oplocks see the CIFS
              spec.

              Currently, if "kernel oplocks" are  supported  then
              level2 oplocks are not granted (even if this param-
              eter is set to "true"). Note  also,  the  "oplocks"
              parameter  must  be  set to "true" on this share in
              order for this parameter to have any effect.

              See also the "oplocks" and "kernel oplocks" parame-
              ters.

              Default:
               level2 oplocks = False

              Example:
               level2 oplocks = True


       oplocks (S)

              This boolean option tells  smbd  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 envi-
              ronments  (it is turned on by default in Windows NT
              Servers).   For  more  information  see  the   file
              Speed.txt in the Samba docs/ directory.

              Oplocks  may  be  selectively turned off on certain
              files on a per share basis.  See the  �veto  oplock
              files�  parameter. On some systems oplocks are rec-
              ognized 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 kernel oplocks parame-
              ter for details.

              See also the "kernel oplocks" and "level2  oplocks"
              parameters.

              Default:      oplocks = True

              Example:      oplocks = False

���Ԃ�A�Ō�̐ݒ肪�֌W���Ă���񂶂�Ȃ����ȁB

> �������A������d�I�[�v���̂����Ȃ�΁A�����ƕp�ɂɏo��悤�ɂ��v���̂ł����c

�ӊO�ƁA���̃t�@�C���ł͓����ɃI�[�v�����Ă邱�Ƃ�
���Ȃ������肷��̂����B

-- 
 �� (�킽���̂������͕l���s�A�A�J�E�~�K���̂ӂ邳�Ƃ̊X)
   <kgh12351@xxxxxxxxxxx> : Taketoshi Sano (����@���r)