search for: fast_share_modes

Hi, How do I enable FAST_SHARE_MODES? In UNIX_INSTALL.html I found (...) See also the FAST_SHARE_MODES option in the Makefile (...) but in my Makefile I didn't found this Flag, even though I read somewhere that this Flag is set as default when compiled for Linux systems. Where and how exactly do I set this Flag? I have a Linux...

...server running SAMBA to share files. The performance seems ok when compared to FTP but our bookkeeping application has it's data as a database stored in a file on the server and the performance for that application is terrible. Investigating this problem I have run across the compiletime option FAST_SHARE_MODES but I have also run across information that tells me this isn't used in current verions of SAMBA or that it is compiled in by default. Can anybody please tell me what is correct. And if you have any other ideas onhow to solve my problem I would gratly appriciate them. Computer config: Dual Ce...

...ode handling in Samba is now much higher than it was previously. PC database packages should be much safer when run against a Samba share. Thanks to Silicon Graphics for testing this code for us. If at all possible compile Samba to use the new share mode handling with shared memory (set the flags FAST_SHARE_MODES in the Makefile). This will be *much* faster than old file-based share modes. FAST_SHARE_MODES have been turned on by default on the following platforms in the Makefile : Linux Solaris BSDI IRIX 5.x.x FreeBSD Updated smb.conf documentation ------------------------------ All options are now d...

...are mode handling in Samba is now much higher than it was previously. PC database packages should be safe when run against a Samba share. Thanks to Silicon Graphics for testing this code for us. If at all possible compile Samba to use the new share mode handling with shared memory (set the flags FAST_SHARE_MODES in the Makefile). This will be *much* faster than old file-based share modes. FAST_SHARE_MODES have been turned on by default on the following platforms in the Makefile : Linux Solaris BSDI IRIX 5.x.x FreeBSD Roving profile support. ----------------------- Roving profiles are believed to wo...

My whole problem as far as samba was concerned was not compiling with DES support *and* that I did compile with FAST_SHARE_MODES. One clue was this in the samba.log. file. I then did a dejanews search for smb_shm_open and came up with that portion of the solution. ERROR smb_shm_open : mmap failed with code 11 The DES portion came from just reading the WinNT.txt file that came with Samba. I can now connect to my Win95 ma...

...ntage of GUEST_SESSSETUP being a compile time parameter, JdL> instead of having it as an smb.conf parameter? I'd like to second this question! Also, just in case that it will not become an smb.conf parameter: can't it be added as a comment to the Makefile (probably near the comments to FAST_SHARE_MODES)? I'm doing ALL the necessary changes for my companies platforms in the Makefile only and am using a line FLAGSM = -DSVR4 -DSHADOW_PWD -DGUEST_SESSSETUP=1 -DFAST_SHARE_MODES -DALLOW_CHANGE_PASSWORD regards Stefan -- Stefan Kanthak e-mail: Stefan.Kanthak@mch.sni.de OEC...

...to the version currently in BRANCH_NTDOM. > Specifically > how is smbstatus getting the information. through locking.c, which has a higher order function table. one of the things that can be done is to enumerate through the open files and open sessions, regardless of whether you are doing FAST_SHARE_MODES (locking_shm.c) or the old slow file-based share modes (locking_slow.c) > By some sort of interprocess communication > with the smbd processes? correct. i'm just having to look at this, to be able to imlement "remote" smbstatus commands in smbclient. luke <a href=&quo...

...on software (patch bundles) released in december 1997 are > installed on both machines. Please find more technical details further > on. I tested this with release 1.8.18p2 and the latest version > 1.8.18p4. and both versions generate the same problem. When compiling > SAMBA without the FAST_SHARE_MODES I was able to avoid this problem > but > I was using this option with older versions of samba so I would like > to > keep it as it is faster :-). > > Did anyone experience the same problem before ? > > The problem is not there when running SAMBA 1.9.17p3. Most of them are...

Hi Jeremy, thanks for the tip but ...(there's always a but) if I do this (increase MAX_OPEN_FILES to 1024), I get an error in log.smb: Can't create or use IPC area. Error was File exists I'm using FAST_SHARE_MODES to compile samba. Does this take up too much space or is there something else wrong? Bye, Jeremy Allison wrote: > > franky.vanliedekerke@mcd.alcatel.be wrote: > > > > Hi, > > > > does anybody have any suggestions about options to put on/off when > > using cle...

...tempt to edit the same record, Tracker refuses the second request if a Win95 server or NT server is used, but allows the second request if a Samba server is used. Subsequently, the data files under Samba become corrupted. We have tried various versions of Samba including 1.9.18p8 with and without FAST_SHARE_MODES, and they all seem to exhibit the same problem. Preliminary debugging shows lots of fcntl_lock calls being performed on zero length files such as MXZD.LCK. The locks being applied at the Unix level are all read locks (non exclusive - so that they are all allowed). The offsets in many cases are (...

The shared mem size option is set to 102400 by default and change is discouraged: The man page (1.9.18p10) says: This parameter is only useful when Samba has been compiled with FAST_SHARE_MODES. It specifies the size of the shared memory (in bytes) to use between smbd processes. You should never change this parameter unless you have studied the source and know what you are doing. This parameter defaults to 1024 multiplied by the setting of the maximum number of open files i...

Samba 1.9.17p1. The log file contains Ks of messages like this: ERROR: set_share_mode: failed to ftruncate share mode file /usr/adm/locks/share.119542272.430101 to size 64 (Permission denied) ERROR: set_share_mode: failed to ftruncate share mode file /usr/adm/locks/share.119542272.430101 to size 64 (Permission denied) ERROR: set_share_mode: failed to ftruncate share mode file

Hello! I've seen, some people experienced this problem earlyer, but I have not found any solution in the mailing lists... So the problem is, copying files from an NT Workstation (SP5 ) on a Samba server running under Linux (2.0.10) in some (rare) cases results in files exactly of the right size but filled with NULL bytes. I'm using samba 2.0.5a and likely since version 2.0.0 this

...donated by Norm Jacobs of Sun Microsystems. Sun have also made a Solaris SPARC workstation available to the Samba Team to aid in their porting efforts. Samba now contains an implementation of share modes using System V shared memory as well as the mmap() based code. This was done to allow the 'FAST_SHARE_MODES' to be used on more systems (especially HPUX 9.x) that have System V shared memory, but not the mmap() call. The System V shared memory code is used by default on many systems as it has benchmarked as faster on many systems. The Automount code has been slightly re-shuffled, such that the home...

...er) I am running samba 1.9.17alpha4 and Linux kernel version 2.0.30. on an AMD486DX4 with 8Mb I have tried the following to fix it without success: 1) tried samba 1.9.16p11, 2) tried Linux kernel version 2.0.27. 3) recompiling everything (kernel and samba) with the latest gcc (2.7.2.2) 4) trying FAST_SHARE_MODES on and off 5) Removing all unneccessary daemons and drivers. 6) Adding more memory 7) changing IRQ's etc 8) Changing my IDE controller 9) Fiddling in the BIOS settings 10) Sacrificing chickens ;-) Nothing makes any difference. Maybe it's just my flaky old 486 to blame. If somebody out the...

...ameter may now be used without recompiling. Much of the internals of Samba has been re-structured to support the oplock and Domain controller changes. Samba now contains an implementation of share modes using System V shared memory as well as the mmap() based code. This was done to allow the 'FAST_SHARE_MODES' to be used on more systems (especially HPUX 9.x) that have System V shared memory, but not the mmap() call. The System V shared memory code is used by default on many systems as it has benchmarked as faster on many systems. The Automount code has been slightly re-shuffled, such that the home...

...lient may ask for DENY_NONE, DENY_READ, DENY_WRITE or DENY_ALL. There are also special compatability modes called DENY_FCB and DENY_DOS. You can disable share modes using "share modes = no". This may be useful on a heavily loaded server as the share modes code is very slow. See also the FAST_SHARE_MODES option in the Makefile for a way to do full share modes very fast using shared memory (if your OS supports it). MAPPING USERNAMES ================= If you have different usernames on the PCs and the unix server then take a look at the "username map" option. See the smb.conf man page f...

...ameter may now be used without recompiling. Much of the internals of Samba has been re-structured to support the oplock and Domain controller changes. Samba now contains an implementation of share modes using System V shared memory as well as the mmap() based code. This was done to allow the 'FAST_SHARE_MODES' to be used on more systems (especially HPUX 9.x) that have System V shared memory, but not the mmap() call. The System V shared memory code is used by default on many systems as it has benchmarked as faster on many systems. The Automount code has been slightly re-shuffled, such that the home...

...ameter may now be used without recompiling. Much of the internals of Samba has been re-structured to support the oplock and Domain controller changes. Samba now contains an implementation of share modes using System V shared memory as well as the mmap() based code. This was done to allow the 'FAST_SHARE_MODES' to be used on more systems (especially HPUX 9.x) that have System V shared memory, but not the mmap() call. The System V shared memory code is used by default on many systems as it has benchmarked as faster on many systems. The Automount code has been slightly re-shuffled, such that the home...

...ameter may now be used without recompiling. Much of the internals of Samba has been re-structured to support the oplock and Domain controller changes. Samba now contains an implementation of share modes using System V shared memory as well as the mmap() based code. This was done to allow the 'FAST_SHARE_MODES' to be used on more systems (especially HPUX 9.x) that have System V shared memory, but not the mmap() call. The System V shared memory code is used by default on many systems as it has benchmarked as faster on many systems. The Automount code has been slightly re-shuffled, such that the home...