Re: NOACL leads to a massive speed slowdown in file system processes

Re: NOACL leads to a massive speed slowdown in file system processes

[tiwasey]

> This is not the default exactly because of its nature.
> It is unusable. You will not be able to run scripts from such mount point.

No problem for me, I have my scripts in my cygwin home/bin. Why put them outside? That's their environment.

> However, I don't quite understand the nature of the issue here. Why not assume
> all files "executable", and only check the magic word, when we actually trying
> to execute them?

True.
Or all normal files like exe, com, bat, sh as executable, and the other ones manually with chmod. That information could be saved in a sqlite DB. Just an idea ;)

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: NOACL leads to a massive speed slowdown in file system processes

[Andrey Repin]

Greetings, tiwasey@arcor.de!

I would really appreciate, if you teach your mail agent to insert proper
threading headers.
Thank you in advance.

>> This is not the default exactly because of its nature.
>> It is unusable. You will not be able to run scripts from such mount point.

> No problem for me, I have my scripts in my cygwin home/bin. Why put them
> outside? That's their environment.

Because my $HOME on noacl mount. In fact it is matching my %USERPROFILE%.

>> However, I don't quite understand the nature of the issue here. Why not assume
>> all files "executable", and only check the magic word, when we actually trying
>> to execute them?

> True.
> Or all normal files like exe, com, bat, sh as executable, and the other
> ones manually with chmod. That information could be saved in a sqlite DB. Just an idea ;)

I would say, "just trust ACLs".
The cases of filesystem not supporting any ACL whatsoever being used with
Cygwin are very rare nowadays.


-- 
With best regards,
Andrey Repin
Monday, September 14, 2015 21:40:03

Sorry for my terrible english...


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: NOACL leads to a massive speed slowdown in file system processes

[Andrey Repin]

Greetings, Mikkel Filla!

> Wow, that seems a very fast solution. Are there any side effects which
> could be a problem? Else I wonder, why this is not the default setting.

This is not the default exactly because of its nature.
It is unusable. You will not be able to run scripts from such mount point.
However, I don't quite understand the nature of the issue here. Why not assume
all files "executable", and only check the magic word, when we actually trying
to execute them?


-- 
With best regards,
Andrey Repin
Sunday, September 13, 2015 21:21:28

Sorry for my terrible english...


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: NOACL leads to a massive speed slowdown in file system processes

[Mikkel Filla]

Wow, that seems a very fast solution. Are there any side effects which
could be a problem? Else I wonder, why this is not the default setting.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: NOACL leads to a massive speed slowdown in file system processes

[Bengt Larsson]

Bengt Larsson wrote:

>Try adding the "notexec" option. If it's mounted "noacl" Cygwin checks
>for executable by opening the file and checking the two first bytes.

If you add "notexec" scripts that start with "#!" won't be recognized as
executable. But files with .exe and .com extensions will be recognized.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: NOACL leads to a massive speed slowdown in file system processes

[Bengt Larsson]

tiwasey@arcor.de wrote:
>Hello, I've used Cygwin under WinXP and now Win8.1. Among others I'm using it to rsync big folders.  I had one big problem. On the destination the file system permissions where that wrong, that I could not enter the rsynced folders. As it is said in the internet, the solution for this is to use NOACL as fstab option. But that leads to massive speed slowdown. rsync processes took around 10 times as before. The same for du on a complex directory. Without NOACL it needed in one example 5sec and with NOACL around 10 minutes. So it seems like that the NOACL option leads to problems with file system processes. Whats the reason and is there a solution for that?
>
>Thank you for helping.

Try adding the "notexec" option. If it's mounted "noacl" Cygwin checks
for executable by opening the file and checking the two first bytes.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

NOACL leads to a massive speed slowdown in file system processes

[tiwasey]

Hello, I've used Cygwin under WinXP and now Win8.1. Among others I'm using it to rsync big folders.  I had one big problem. On the destination the file system permissions where that wrong, that I could not enter the rsynced folders. As it is said in the internet, the solution for this is to use NOACL as fstab option. But that leads to massive speed slowdown. rsync processes took around 10 times as before. The same for du on a complex directory. Without NOACL it needed in one example 5sec and with NOACL around 10 minutes. So it seems like that the NOACL option leads to problems with file system processes. Whats the reason and is there a solution for that?

Thank you for helping.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple