Re: 5 seconds to update link info?

2017-05-19 Thread L A Walsh

Andrey Repin wrote:

Greetings, All!

_a=fileA;
_b=fileB;
[ ! -f "$_a" ] && touch "$_a";
[ ! -f "$_b" ] && ln "$_a" "$_b";
for i in $(seq 1 10);
do sleep 1;
[ "$_a" -ef "$_b" ] && { echo Timed in $i; break;}; done;
rm "$_a" "$_b"

When executed this oneliner over Samba 4.3 network share,


   What oneliner?



--
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: 5 seconds to update link info?

2017-05-19 Thread Andrey Repin
Greetings, Richard H Lee!

> On 19/05/2017 23:01, Richard H Lee wrote:
>> On 19/05/2017 22:37, Andrey Repin wrote:
>>> When executed this oneliner over Samba 4.3 network share, it takes 5
>>> seconds to match the newly created hardlink. I'm wondering if this is
>>> Cygwin, Samba or Windows networking issue?
>> 
>> I think it's something to do with windows name resolution.
>> 
>> Try running:
>> ls //
>> 
>> You should see a similar delay.

> I forgot to mention that you can get rid of this delay by disabling
> NetBIOS on your active network connection(s). I don't think this should
> interfere with the operation of Samba.

I've tried to disable NetBIOS over TCP/IP on client for all adapters active,
but nothing has changed.


-- 
With best regards,
Andrey Repin
Saturday, May 20, 2017 03:35:13

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: 5 seconds to update link info?

2017-05-19 Thread Richard H Lee

On 19/05/2017 23:01, Richard H Lee wrote:

On 19/05/2017 22:37, Andrey Repin wrote:

When executed this oneliner over Samba 4.3 network share, it takes 5
seconds to match the newly created hardlink. I'm wondering if this is
Cygwin, Samba or Windows networking issue?


I think it's something to do with windows name resolution.

Try running:
ls //

You should see a similar delay.


I forgot to mention that you can get rid of this delay by disabling
NetBIOS on your active network connection(s). I don't think this should
interfere with the operation of Samba.

--
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: 5 seconds to update link info?

2017-05-19 Thread Richard H Lee

On 19/05/2017 22:37, Andrey Repin wrote:

When executed this oneliner over Samba 4.3 network share, it takes 5
seconds to match the newly created hardlink. I'm wondering if this is
Cygwin, Samba or Windows networking issue?


I think it's something to do with windows name resolution.

Try running:
ls //

You should see a similar delay.

--
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



5 seconds to update link info?

2017-05-19 Thread Andrey Repin
Greetings, All!

_a=fileA;
_b=fileB;
[ ! -f "$_a" ] && touch "$_a";
[ ! -f "$_b" ] && ln "$_a" "$_b";
for i in $(seq 1 10);
do sleep 1;
[ "$_a" -ef "$_b" ] && { echo Timed in $i; break;}; done;
rm "$_a" "$_b"

When executed this oneliner over Samba 4.3 network share, it takes 5 seconds
to match the newly created hardlink.
I'm wondering if this is Cygwin, Samba or Windows networking issue?


-- 
With best regards,
Andrey Repin
Saturday, May 20, 2017 00:31:35

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: SSH Keys breaking symlink access?

2017-05-19 Thread Erik Soderquist
On Fri, May 19, 2017 at 5:30 PM, Erik Soderquist wrote:
> This is expected behavior if you have not used "password -R" to
> provide the network password.


from the doc 
(https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-setuid-overview):
So what we do is to utilize this registry area for the purpose of
set(e)uid. The Cygwin command passwd -R allows a user to specify
his/her password for storage in this registry area. When this user
tries to login using ssh with public key authentication, Cygwin's
set(e)uid examines the LSA private registry area and searches for a
Cygwin specific key which contains the password. If it finds it, it
calls LogonUser under the hood, using this password. If that works,
LogonUser returns an access token with all credentials necessary for
network access.


-- Erik

--
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: SSH Keys breaking symlink access?

2017-05-19 Thread Erik Soderquist
On Fri, May 19, 2017 at 3:26 PM,  Dave Pierce wrote:
> Hello!
>
> I am running Cygwin-64, 2.8.0(0.309/5/3) on a Windows 2016 Server. This
> system is intended for use by a fairly wide audience of devs. We have this
> working correctly on an old Windows 2008 box running Cygwin
> 1.7.9(0.237/5/3).
> The new system is intended to replace the old one. I've mimicked the
> configuration as much possible on the new system, but am running
> into an issue with passwordless (key-auth) ssh.

Did you set up the daemon and use "passwd -R"?

> I have created a windows symlink ("mklink /d /sharename [unc_path]") in
> the c:\cygwin64 directory that points to an NFS share. (This is the same
> as the old system.)
>
> I have OpenSSH configured and working.
>
> I can access "/sharename" within explorer (c:\cygwin64\sharename\)
> and locally from within the Cygwin prompt (/sharename), when
> logged in as either the service account or my own domain account.
>
> If I ssh into the system using password authentication, I am able to
> "ls /sharename" regardless of which account I use, in either
> interactive mode or not.
>
> If I copy ~/.ssh/ to the server for the service account, I can get into
> /sharename.
>
> But if I copy ~/.ssh/ for my own domain account, I cannot. I get a
> "permission denied" error when attempting to cd to /sharename or
> do an ls of it. Th= is is true whether I ssh into the system
> interactively, or execute the command remotely / non-interactively.

This is expected behavior if you have not used "password -R" to
provide the network password.

-- Erik

--
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



[ANNOUNCEMENT] Updated: mintty 2.7.7

2017-05-19 Thread Thomas Wolff

I have uploaded mintty 2.7.7 with the following changes:

Font rendering and display handling
  * Automatically disabling Uniscribe for ASCII-only chunks 
(mintty/wsltty#36).
  * Fixed bidi display while showing other screen with Bidi=1 (#592, 
~#392, ~#605).


Window handling
  * Avoid being pushed behind other windows on Ctrl+TAB (#652).
  * Tweaks to stabilize initial window geometry (#629, #649).
  * Fixed broken size parameters maxwidth/maxheight.

Terminal handling
  * Option NoAltScreen disables the alternate screen (~#652).
  * Fixed delayed scroll marker highlighting (#569).
  * Manual: link to Wiki about console issues / winpty wrapper (#650).

Configuration
  * New option --configdir for config file and resource folders 
(mintty/winpty#30, mintty/winpty#40, mintty/winpty#38).
  * Always save to config file specified with -c/--config or 
--configdir (mintty/winpty#30, ~mintty/winpty#40).
  * Options: offer resources from subdirectories of all config 
directories (#639, #30, ~#38).
  * Configuration resource subdirectories are created as needed (#30, 
#38, ~#639).


Other
  * Fixed cleanup of environment variables after user command (#654).
  * Fixed usage of /tmp or (if read-only) alternatives (mintty/wsltty#30).
  * Wiki: removed link to buggy themes (#647).

The homepage is at http://mintty.github.io/
It also links to the issue tracker.

--
Thomas

--
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



SSH Keys breaking symlink access?

2017-05-19 Thread Dave.Pierce
Hello!

I am running Cygwin-64, 2.8.0(0.309/5/3) on a Windows 2016 Server. This sys= 
tem is intended for use by a fairly wide audience of devs. We have this wor= 
king correctly on an old Windows 2008 box running Cygwin 1.7.9(0.237/5/3). = 
The new system is intended to replace the old one. I've mimicked the config= 
uration as much possible on the new system, but am running into an issue wi= th 
passwordless (key-auth) ssh.

I have created a windows symlink ("mklink /d /sharename [unc_path]") in the=
 c:\cygwin64 directory that points to an NFS share. (This is the same as th= e 
old system.)

I have OpenSSH configured and working.

I can access "/sharename" within explorer (c:\cygwin64\sharename\) and loca= 
lly from within the Cygwin prompt (/sharename), when logged in as either th= e 
service account or my own domain account.

If I ssh into the system using password authentication, I am able to "ls /s= 
harename" regardless of which account I use, in either interactive mode or = 
not.

If I copy ~/.ssh/ to the server for the service account, I can get into /sh= 
arename.

But if I copy ~/.ssh/ for my own domain account, I cannot. I get a "permiss= 
ion denied" error when attempting to cd to /sharename or do an ls of it. Th= is 
is true whether I ssh into the system interactively, or execute the comm= and 
remotely / non-interactively.

On the old system, "ls -la /" shows the link owned by the service account u= 
ser. On the new system, it was initially owned by "Administrators" but I ch= 
anged it to match. This did not change behavior. I've diffed the other Cygw= in 
config files and except for a couple minor tweaks due to the newer Cygwi= n 
version, there are no differences.

/var/log/sshd.log shows nothing.

Any help or troubleshooting tips would be appreciated. I'm not so hot as a = 
Windows admin - without dmesg or a syslog, I'm kind of at a loss. I don't 
really understand why ssh key auth would interfere with file system or network 
access in this way.

Regards,
Dave P.


--
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



[ATTN: Yaakov Selkowitz / PHP maintainer] Re: Composer segfault on multiple configurations

2017-05-19 Thread Richard H Lee

On 18/05/2017 08:42, Sky Diver wrote:

Any idea when your fix will get released as an official cygwin PHP
package?


Hi Yaakov,

I can see you're really busy with package maintenance and all, but I was
wondering if you could review and merge my patch for this issue. It's
basically changing the definition of the page size in two places.


Richard
diff --git a/Zend/zend_stream.c b/Zend/zend_stream.c
index 3fd7fa0..f5b9bea 100644
--- a/Zend/zend_stream.c
+++ b/Zend/zend_stream.c
@@ -30,7 +30,11 @@
 # if HAVE_UNISTD_H
 #  include 
 #  if defined(_SC_PAGESIZE)
+#   ifdef __CYGWIN__
+#define REAL_PAGE_SIZE 4096
+#   else
 #define REAL_PAGE_SIZE sysconf(_SC_PAGESIZE);
+#   endif
 #  elif defined(_SC_PAGE_SIZE)
 #define REAL_PAGE_SIZE sysconf(_SC_PAGE_SIZE);
 #  endif
diff --git a/main/main.c b/main/main.c
index 01ed3a6..0909309 100644
--- a/main/main.c
+++ b/main/main.c
@@ -96,7 +96,11 @@
 # if HAVE_UNISTD_H
 #  include 
 #  if defined(_SC_PAGESIZE)
+#   ifdef __CYGWIN__
+#define REAL_PAGE_SIZE 4096
+#   else
 #define REAL_PAGE_SIZE sysconf(_SC_PAGESIZE);
+#   endif
 #  elif defined(_SC_PAGE_SIZE)
 #define REAL_PAGE_SIZE sysconf(_SC_PAGE_SIZE);
 #  endif

--
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: setup-x86.exe default view

2017-05-19 Thread cyg Simple
On 5/19/2017 8:40 AM, Nellis, Kenneth wrote:
> From: Sky Diver 
>> Actually, the preferred user experience would be to:
>> 1. Start in Category view
>> 2. Select whatever packages to install/remove/etc.
>> 3. Click "Next"
>> 4. Have the Pending view show up in order to review whatever is going
>> to be installed.
>> 5. Have the option to Approve / Cancel / Go Back

I like this scenario

> 
> I am perfectly happy with the current Setup; however I would 
> be surprised if the typical user did not launch Setup mainly 
> to update packages already installed. 

The be surprised.  I typically don't run setup unless I need something
new.  I might update once a year.

> Accordingly, Pending is the logical view to show first.

Says you, but I don't agree.  It's confusing.

> But I recognize that it would 
> be good to also show Pending as the last stage before actual 
> installation. Therefore, if changes are made to Setup, perhaps 
> start with Pending. If anything is added or deleted by going 
> off the Pending view, then Next should take you back to 
> Pending for a final review before actual installation.
> 

-- 
cyg Simple

--
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: Building modules for perl-5.24

2017-05-19 Thread Ken Brown

On 5/18/2017 3:00 PM, Achim Gratz wrote:

I hope I've gleaned all the dependencies of biber correctly, so this
should be your dependency tree for perl-5.24.1 (the first few have a
cycle somewhere in their dependencies, so you need to build them, then
start from the top again, they're the ones that are indented "too far"):


Thanks!

Ken


--
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: Building modules for perl-5.24

2017-05-19 Thread Ken Brown

On 5/18/2017 3:12 PM, Brian Inglis wrote:

On 2017-05-18 13:00, Achim Gratz wrote:

Ken Brown writes:


Should this discussion have been taking place on -apps?


Probably.


Relative newbie on apps but feel I've become apps-cop ;^>
I've got my eyes on you - Brown!


Sorry, Officer.

Ken


--
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: setup-x86.exe default view

2017-05-19 Thread Nellis, Kenneth
From: Sky Diver 
> Actually, the preferred user experience would be to:
> 1. Start in Category view
> 2. Select whatever packages to install/remove/etc.
> 3. Click "Next"
> 4. Have the Pending view show up in order to review whatever is going
> to be installed.
> 5. Have the option to Approve / Cancel / Go Back

I am perfectly happy with the current Setup; however I would 
be surprised if the typical user did not launch Setup mainly 
to update packages already installed. Accordingly, Pending is 
the logical view to show first. But I recognize that it would 
be good to also show Pending as the last stage before actual 
installation. Therefore, if changes are made to Setup, perhaps 
start with Pending. If anything is added or deleted by going 
off the Pending view, then Next should take you back to 
Pending for a final review before actual installation.

--Ken Nellis


Re: setup-x86.exe default view

2017-05-19 Thread Sky Diver
On Thu, May 18, 2017 at 9:35 PM, Brian Inglis wrote:
> You should always check Pending last, to see what will be installed
> or upgraded, if there is anything you forgot, don't need, or don't
> want upgraded, and the download sizes, if time, speed, or space are
> concerns, or you just don't want a pile of time or space used up by
> some bloated packages.

Actually, the preferred user experience would be to:
1. Start in Category view
2. Select whatever packages to install/remove/etc.
3. Click "Next"
4. Have the Pending view show up in order to review whatever is going
to be installed.
5. Have the option to Approve / Cancel / Go Back

This way, the Pending view is shown at the right moment (after setup
instead of before) so there's no need to remember to manually do that.
Personally I don't use the setup program too often so I don't think
I'll remember to do that each time, especially when most setup
programs will show you a final summary with the list of files/packages
that would be installed and the amount of required disk space - prior
to installing the software - and will also wait for confirmation (even
text-based installers like apt-get, for example, behave like that).

--
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