[CentOS] Samba "use sendfile" configuration option set do disabled as default - why?
happymaster23 at gmail.com
Tue Aug 25 09:44:18 UTC 2009
No, I have not any problem. With use sendfile = yes it works great. My
question is, why is this configuration option set to be off in CentOS?
You know - when I want to read something about oplocks (advantages &
disadvantages) it was very easy - there are tons of documentation.
When I want to read something about use sendfile, it is big problem,
becuse there is nothing.
My question is why is this option disabled as default in CentOS? And I
am not alone with this question -
It is two WD Caviar GP in SW RAID 1 and LVM2, so there can´t be a problem.
2009/8/25 JohnS <jses27 at gmail.com>:
> On Mon, 2009-08-24 at 19:01 +0200, happymaster23 wrote:
>> This is not problem of disks, this is problem of Samba (operating
>> systems in network are Windows XP and Windows 7 only, so this should
>> not be problem caused by Windows).
>> I am asking because of risks and disadvantages. This is same as
>> oplocks - it may be performance tweak, but it is potentially dangerous
>> (data corruption).
> If you are using XP and Vista you should not need it. I did not say it
> was a disk problem either. Please bottom post all replies. All it really
> does is keep an in memory copy. If the server is heavily loaded you can
> start swapping witch will farther reduce performance. Also like the man
> page says read raw = yes can be set also with out sendfile. Problem, you
> really dont say what the exact problem is...Slow?
> CentOS mailing list
> CentOS at centos.org
More information about the CentOS