Re: Ability to specify /cygdrive mount value in setup

[Andrey Repin]

Greetings, cyg Simple!

> I find /cygdrive/ just unbearable and I always change it to / after an
> install.  The issue with this is that post install activities will
> create symlinks using /cygdrive moniker so I must go change those if I
> find them.

Just which activities?
I haven't seen any. And I do remap /cygdrive to / at all times.

> Would it be possible for setup to ask for the value and
> setup the /etc/fstab with the value?  Do others find this bit of annoying?

You can precreate fstab, I think.


-- 
With best regards,
Andrey Repin
Wednesday, November 25, 2015 19:38:07

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

Ability to specify /cygdrive mount value in setup

[cyg Simple]

Friends,

I find /cygdrive/ just unbearable and I always change it to / after an
install.  The issue with this is that post install activities will
create symlinks using /cygdrive moniker so I must go change those if I
find them.  Would it be possible for setup to ask for the value and
setup the /etc/fstab with the value?  Do others find this bit of annoying?

-- 
Regards,
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: Ability to specify /cygdrive mount value in setup

[Eliot Moss]

On 11/25/2015 10:56 AM, cyg Simple wrote:


I find /cygdrive/ just unbearable and I always change it to / after an
install.  The issue with this is that post install activities will
create symlinks using /cygdrive moniker so I must go change those if I
find them.  Would it be possible for setup to ask for the value and
setup the /etc/fstab with the value?  Do others find this bit of annoying?


I just create symlinks so that in the cygwin universe /c means /cygdrive/c,
etc.  So, not a link of /, but individual links for the drives I use.
These survive updates, anyway.  It's been a long time since I've wiped
everything and installed from scratch, though.  If that's what you're
talking about, then my suggestion would not be helpful ...

Regards -- Eliot Moss

--
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: binutils-2.25-4 (x86_64)

[JonY]

Built against master 3f8a753391fbd7807d6e4ef33a5b48b7bc43086b, now for
64bit Cygwin.

This version should fix the "nm -l" slowdown problem, including
incorporating all previous patches. Dwarf Errors were also happening for
64bit, but was less noticeable.

There is no -3 release, to match the x86 version bump.

  *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there. It will be in the format:

cygwin-announce-unsubscribe-you=yourdomain.com  cygwin.com

If you need more information on unsubscribing, start reading here:

http://sourceware.org/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is available
starting at this URL.




signature.asc
Description: OpenPGP digital signature

Updated: binutils-2.25-4 (x86_64)

[JonY]

Built against master 3f8a753391fbd7807d6e4ef33a5b48b7bc43086b, now for
64bit Cygwin.

This version should fix the "nm -l" slowdown problem, including
incorporating all previous patches. Dwarf Errors were also happening for
64bit, but was less noticeable.

There is no -3 release, to match the x86 version bump.

  *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there. It will be in the format:

cygwin-announce-unsubscribe-you=yourdomain.com  cygwin.com

If you need more information on unsubscribing, start reading here:

http://sourceware.org/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is available
starting at this URL.




signature.asc
Description: OpenPGP digital signature

Re: Mintty 2.2.2: possible hang when breaking (CTRL+C) out of pinging unresponsive host

[Ken Brown]

On 11/25/2015 4:03 PM, Marco Atzeri wrote:

On 25/11/2015 20:52, Jim Reisert AD1C wrote:

[LTDENA-REISERT:~] $ which ping
/usr/bin/ping

[LTDENA-REISERT:~] $ ls -l `which ping`
-rwxr-xr-x 1 reisert Domain Users 13824 May  3  2014 /usr/bin/ping



you have an alias somewhere


Not necessarily.  He might have the Cygwin ping package installed.

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: Mintty 2.2.2: possible hang when breaking (CTRL+C) out of pinging unresponsive host

[Thomas Wolff]

Am 25.11.2015 um 23:44 schrieb Ken Brown:

On 11/25/2015 4:03 PM, Marco Atzeri wrote:

On 25/11/2015 20:52, Jim Reisert AD1C wrote:

[LTDENA-REISERT:~] $ which ping
/usr/bin/ping

[LTDENA-REISERT:~] $ ls -l `which ping`
-rwxr-xr-x 1 reisert Domain Users 13824 May  3  2014 /usr/bin/ping



you have an alias somewhere


Not necessarily.  He might have the Cygwin ping package installed.

Ken
The point is that his ping is likely to be the Windows ping, judging by 
its output format, despite the output of `which` which may be false. It 
is better to use `type`.


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

mksnt sh is invoked when executing cygwin icon;

[Kenneth Wolcott]

Hi;

  It seems that a 32bit Windows server with a pre-existing MKS Toolkit
installation prevents an interactive Cygwin window (mintty) from
starting properly.

  If the c:\mksnt directory (where MKS Tookkit is installed) is
renamed to c:\NOTmksnt, then double-clicking the Cygwin icon results
in:

"Failed to run C:/mksnt/sh.exe: No such file or directory"

But if the c:\NOTmksnt directory is renamed back to what it was, then
the window opens up with sh.exe from mksnt instead of bash and seems
to hang for a very long time.

   Why is this?  Part of me thinks that Cygwin and MKS Toolkit should
just coexist just fine, each not knowing about the other (c:\cygwin
and c:\mksnt).  Part of me thinks that I'd like to have Cygwin come
first in the path rather than having c:\mksnt first in the path.  Is
there a way to force the Cygwin install process (or fix it afterward)
to put Cygwin first?

  I tried to change /etc/profile so that the PATH variable was set to
exclusively Cygwin stuff, but that had no effect.

  How to fix this outside Cygwin? (The Windows side)

  How to fix this inside Cygwin?

Thanks,
Ken Wolcott

--
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: Mintty 2.2.2: possible hang when breaking (CTRL+C) out of pinging unresponsive host

[Jim Reisert AD1C]

[LTDENA-REISERT:~] $ which ping
/usr/bin/ping

[LTDENA-REISERT:~] $ ls -l `which ping`
-rwxr-xr-x 1 reisert Domain Users 13824 May  3  2014 /usr/bin/ping

-- 
Jim Reisert AD1C, , http://www.ad1c.us

--
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: Mintty 2.2.2: possible hang when breaking (CTRL+C) out of pinging unresponsive host

[Thomas Wolff]

Am 25.11.2015 um 19:51 schrieb Jim Reisert AD1C:

On Wed, Nov 25, 2015 at 4:03 AM, Marco Atzeri wrote:


you are right is not a mintty only issue.
Same happens in xterm


$ which ping
/usr/bin/ping

$ ping 2.2.2.2
PING 2.2.2.2 (2.2.2.2): 56 data bytes

It sticks here forever, CTRL+C ineffective.

Worked fine for me using Cygwin64 and Cygwin build 2.4.0(0.292/5/3)

[LTDENA-REISERT:~] $ ping 2.2.2.2

Pinging 2.2.2.2 with 32 bytes of data:

(type CTRL-C here)

[LTDENA-REISERT:~] $
Please note the difference and provide the necessary information (`which 
ping`):

PING 2.2.2.2 (2.2.2.2): 56 data bytes
Pinging 2.2.2.2 with 32 bytes of data: 

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

RE: Ability to specify /cygdrive mount value in setup

[Buchbinder, Barry (NIH/NIAID) [E]]

Andrey Repin sent the following at Wednesday, November 25, 2015 11:39 AM
>On 11/25/2015 10:56 AM, cyg Simple wrote:
>> I find /cygdrive/ just unbearable and I always change it to / after an
>> install.  The issue with this is that post install activities will
>> create symlinks using /cygdrive moniker so I must go change those if I
>> find them.
>
>Just which activities? I haven't seen any. And I do remap /cygdrive to /
>at all times.

I grepped everything in and under /etc for cygdrive.  The only hits were
/etc/fstab and /etc/postinstall/000-cygwin-post-install.sh.done, and the
latter was just setting up the former.  So I have to ask, what's creating
these shortcuts?

The idea that setup or the post-install scripts create symlinks that
point to things that are not under / and need to be accessed as, for
example, /cygdrive/d (= D:\) seems very strange.

>> Would it be possible for setup to ask for the value and
>> setup the /etc/fstab with the value?  Do others find this bit of annoying?
>
>You can precreate fstab, I think.

Maybe you could do a 3-step install?
  -  minimal install.
  -  fix fstab.
  -  install optional packages.

Another (partially tested) idea:  Create a folder in / named /cygdrive.
Then create a symlink in it for each drive, where the symlink points to
the drive and is named as the drive letter.  That seems to work for
some purposes, e.g., cd /cygdrive/d/dir/ goes to /d, though the CWD will
be /cygdrive/d/dir, not /d/DIR.  YMMV.

But pre-creating c:\cygwin\etc\fstab seems like the best option.

Good Luck.

- Barry
  Disclaimer: Statements made herein are not made on behalf of NIAID.

--
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: Ability to specify /cygdrive mount value in setup

[Roger Wells]

On 11/25/2015 10:56 AM, cyg Simple wrote:
> Friends,
> 
> I find /cygdrive/ just unbearable and I always change it to / after an
> install.  The issue with this is that post install activities will
> create symlinks using /cygdrive moniker so I must go change those if I
> find them.  Would it be possible for setup to ask for the value and
> setup the /etc/fstab with the value?  Do others find this bit of annoying?
> 

yep

-- 
Roger Wells, P.E.
leidos
221 Third St
Newport, RI 02840
401-847-4210 (voice)
401-849-1585 (fax)
roger.k.we...@leidos.com

--
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: Mintty 2.2.2: possible hang when breaking (CTRL+C) out of pinging unresponsive host

[Jim Reisert AD1C]

On Wed, Nov 25, 2015 at 4:03 AM, Marco Atzeri wrote:

> you are right is not a mintty only issue.
> Same happens in xterm
>
>
> $ which ping
> /usr/bin/ping
>
> $ ping 2.2.2.2
> PING 2.2.2.2 (2.2.2.2): 56 data bytes
>
> It sticks here forever, CTRL+C ineffective.

Worked fine for me using Cygwin64 and Cygwin build 2.4.0(0.292/5/3)

[LTDENA-REISERT:~] $ ping 2.2.2.2

Pinging 2.2.2.2 with 32 bytes of data:

(type CTRL-C here)

[LTDENA-REISERT:~] $


-- 
Jim Reisert AD1C, , http://www.ad1c.us

--
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: Ability to specify /cygdrive mount value in setup

[Charlie]

Wed, 25 Nov 2015 19:39:08 Andrey wrote:

>>> You can precreate fstab, I think.

Yes I do this all the time.  If, for example, C:\cygwin64\etc\fstab already 
exists
when you run setup-x86_64.exe the first time, setup will use that /etc/fstab.
So all the links will be created during initial installation with / and not 
/cygdrive.



--
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: Ability to specify /cygdrive mount value in setup

[Andrey Repin]

Greetings, Charlie!

> Wed, 25 Nov 2015 19:39:08 Andrey wrote:

 You can precreate fstab, I think.

> Yes I do this all the time.  If, for example, C:\cygwin64\etc\fstab already 
> exists
> when you run setup-x86_64.exe the first time, setup will use that /etc/fstab.
> So all the links will be created during initial installation with / and not 
> /cygdrive.

Just which links we're talking about, yet again?...



-- 
With best regards,
Andrey Repin
Wednesday, November 25, 2015 23:24:47

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: Mintty 2.2.2: possible hang when breaking (CTRL+C) out of pinging unresponsive host

[Andrey Repin]

Greetings, Jim Reisert AD1C!

> [LTDENA-REISERT:~] $ which ping
> /usr/bin/ping

> [LTDENA-REISERT:~] $ ls -l `which ping`
> -rwxr-xr-x 1 reisert Domain Users 13824 May  3  2014 /usr/bin/ping

Well, try again with native ping.


-- 
With best regards,
Andrey Repin
Wednesday, November 25, 2015 23:22:38

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

64bit cygwin 2.4.0-0.4 hangs when pinging unresponsive host

[Marco Atzeri]

On 25/11/2015 12:03, Marco Atzeri wrote:

On 25/11/2015 08:06, Thomas Wolff wrote:

Am 24.11.2015 um 23:29 schrieb Marco Atzeri:





...
I assume it is an interaction with mintty.

Many problems of that kind attributed to mintty are actually problems
with cygwin or especially pty.
Please test also with another terminal (xterm, rxvt, ...).
Also some more details could be helpful as I cannot reproduce the issue
(output of `type ping`, actual host pinged).
--
Thomas


you are right is not a mintty only issue.
Same happens in xterm


$ which ping
/usr/bin/ping

$ ping 2.2.2.2
PING 2.2.2.2 (2.2.2.2): 56 data bytes

It sticks here forever, CTRL+C ineffective.
Process Explorer or Task Manager are needed to kill the process.
Also kill -9 PID is ineffective

On the old cygwin.bat (aka windows cmd)
CTRL+C is effective

  64 $ ping 2.2.2.2
PING 2.2.2.2 (2.2.2.2): 56 data bytes

2.2.2.2 PING Statistics
2 packets transmitted, 0 packets received, 100.0% packet loss



the problem seems restricted to the 64bit test version of cygwin.

$ uname -svm
CYGWIN_NT-6.1 2015-11-21 16:59 x86_64

The issue is not present on 2.3.1

$ ping 2.2.2.2
PING 2.2.2.2 (2.2.2.2): 56 data bytes

2.2.2.2 PING Statistics
2 packets transmitted, 0 packets received, 100.0% packet loss

$ uname -srm
CYGWIN_NT-6.1 2.3.1(0.291/5/3) x86_64


And the 32 bit version is not impacted

$ ping 2.2.2.2
PING 2.2.2.2 (2.2.2.2): 56 data bytes

2.2.2.2 PING Statistics
2 packets transmitted, 0 packets received, 100.0% packet loss

$ uname -srm
CYGWIN_NT-6.1-WOW 2.4.0(0.292/5/3) i686


--
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: Ability to specify /cygdrive mount value in setup

[cyg Simple]

n 11/25/2015 3:25 PM, Andrey Repin wrote:
> Greetings, Charlie!
> 
>> Wed, 25 Nov 2015 19:39:08 Andrey wrote:
> 
> You can precreate fstab, I think.
> 
>> Yes I do this all the time.  If, for example, C:\cygwin64\etc\fstab already 
>> exists
>> when you run setup-x86_64.exe the first time, setup will use that /etc/fstab.
>> So all the links will be created during initial installation with / and not 
>> /cygdrive.
> 
> Just which links we're talking about, yet again?...
> 

find / -type l -exec ls -l {} \; | grep cygdrive

lrwxrwxrwx 1 cyg_Simple cyg_Simple 46 Nov 25 09:29 /etc/hosts ->
/cygdrive/c/WINDOWS/System32/drivers/etc/hosts
lrwxrwxrwx 1 cyg_Simple cyg_Simple 49 Nov 25 09:29 /etc/networks ->
/cygdrive/c/WINDOWS/System32/drivers/etc/networks
lrwxrwxrwx 1 cyg_Simple cyg_Simple 49 Nov 25 09:29 /etc/protocols ->
/cygdrive/c/WINDOWS/System32/drivers/etc/protocol
lrwxrwxrwx 1 cyg_Simple cyg_Simple 49 Nov 25 09:29 /etc/services ->
/cygdrive/c/WINDOWS/System32/drivers/etc/services

I also have the following which indicates that I modified /etc/fstab but
too late.

lrwxrwxrwx 1 cyg_Simple cyg_Simple 0 Nov 25 15:54 /proc/cygdrive -> /

If I were able to specify it at the start of setup this issue would not
be present.

-- 
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: Mintty 2.2.2: possible hang when breaking (CTRL+C) out of pinging unresponsive host

[Marco Atzeri]

On 25/11/2015 20:52, Jim Reisert AD1C wrote:

[LTDENA-REISERT:~] $ which ping
/usr/bin/ping

[LTDENA-REISERT:~] $ ls -l `which ping`
-rwxr-xr-x 1 reisert Domain Users 13824 May  3  2014 /usr/bin/ping



you have an alias somewhere

$ /cygdrive/c/windows/System32/ping 2.2.2.2

Pinging 2.2.2.2 with 32 bytes of data:

--
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: Ability to specify /cygdrive mount value in setup

[Buchbinder, Barry (NIH/NIAID) [E]]

cyg Simple sent the following at Wednesday, November 25, 2015 3:59 PM
>>> Wed, 25 Nov 2015 19:39:08 Andrey wrote:
>>
>> You can precreate fstab, I think.
>>
>>> Yes I do this all the time.  If, for example, C:\cygwin64\etc\fstab already 
>>> exists
>>> when you run setup-x86_64.exe the first time, setup will use that 
>>> /etc/fstab.
>>> So all the links will be created during initial installation with / and not 
>>> /cygdrive.
>>
>> Just which links we're talking about, yet again?...
>>
>
>n 11/25/2015 3:25 PM, Andrey Repin wrote:
>
>find / -type l -exec ls -l {} \; | grep cygdrive
>
>lrwxrwxrwx 1 cyg_Simple cyg_Simple 46 Nov 25 09:29 /etc/hosts ->
>/cygdrive/c/WINDOWS/System32/drivers/etc/hosts
>lrwxrwxrwx 1 cyg_Simple cyg_Simple 49 Nov 25 09:29 /etc/networks ->
>/cygdrive/c/WINDOWS/System32/drivers/etc/networks
>lrwxrwxrwx 1 cyg_Simple cyg_Simple 49 Nov 25 09:29 /etc/protocols ->
>/cygdrive/c/WINDOWS/System32/drivers/etc/protocol
>lrwxrwxrwx 1 cyg_Simple cyg_Simple 49 Nov 25 09:29 /etc/services ->
>/cygdrive/c/WINDOWS/System32/drivers/etc/services
>
>I also have the following which indicates that I modified /etc/fstab but
>too late.
>
>lrwxrwxrwx 1 cyg_Simple cyg_Simple 0 Nov 25 15:54 /proc/cygdrive -> /
>
>If I were able to specify it at the start of setup this issue would not
>be present.

It look like those links are created by /etc/postinstall/base-files-mketc.sh.
You could try just removing /etc/hosts, /etc/protocols, /etc/services, and
/etc/networks, being careful to delete the symlink and not the target, and
then re-run /etc/postinstall/base-files-mketc.sh.done.  After modifying
/etc/fstab, of course.

- Barry
  Disclaimer: Statements made herein are not made on behalf of NIAID.

--
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: [h-e-w] cygwin-64 2.3.1. bash fails when running under FSF emacs 24.5

[Eli Zaretskii]

> Date: Wed, 25 Nov 2015 12:37:15 +0100
> From: Dominique de Waleffe 
> 
> bash: cannot set terminal process group (-1): Inappropriate ioctl for device
> bash: no job control in this shell
> 1 [main] bash 9588 c:\s\cygwin64\bin\bash.exe: *** fatal error in forked
> process - fork: can't reserve memory for parent stack 0x60 - 0x80,
> (child has 0x40 - 0x60), Win32 error 487
> 1115 [main] bash 9588 cygwin_exception::open_stackdumpfile: Dumping stack 
> trace
> to bash.exe.stackdump
> 1 [main] bash 16396 fork: child -1 - forked process 9588 died unexpectedly,
> retry 0, exit code 0x100, errno 11
> bash: fork: retry: No child processes
> 1018684 [main] bash 14236 c:\s\cygwin64\bin\bash.exe: *** fatal error in 
> forked
> process - fork: can't reserve memory for parent stack 0x60 - 0x80,
> (child has 0x40 - 0x60), Win32 error 487
> 1019772 [main] bash 14236 cygwin_exception::open_stackdumpfile: Dumping stack
> trace to bash.exe.stackdump
> 1157135 [main] bash 16396 fork: child -1 - forked process 14236 died
> unexpectedly, retry 0, exit code 0x100, errno 11

These are Cygwin errors, which I hope Cygwin folks will be able to
interpret.  Perhaps the stack dump trace produced by this will help
them even more, so I suggest to post its contents.

--
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: Mintty 2.2.2: possible hang when breaking (CTRL+C) out of pinging unresponsive host

[Marco Atzeri]

On 25/11/2015 08:06, Thomas Wolff wrote:

Am 24.11.2015 um 23:29 schrieb Marco Atzeri:





...
I assume it is an interaction with mintty.

Many problems of that kind attributed to mintty are actually problems
with cygwin or especially pty.
Please test also with another terminal (xterm, rxvt, ...).
Also some more details could be helpful as I cannot reproduce the issue
(output of `type ping`, actual host pinged).
--
Thomas


you are right is not a mintty only issue.
Same happens in xterm


$ which ping
/usr/bin/ping

$ ping 2.2.2.2
PING 2.2.2.2 (2.2.2.2): 56 data bytes

It sticks here forever, CTRL+C ineffective.
Process Explorer or Task Manager are needed to kill the process.
Also kill -9 PID is ineffective

On the old cygwin.bat (aka windows cmd)
CTRL+C is effective

 64 $ ping 2.2.2.2
PING 2.2.2.2 (2.2.2.2): 56 data bytes

2.2.2.2 PING Statistics
2 packets transmitted, 0 packets received, 100.0% packet loss


Regards
Marco

--
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: Symlink targets dereferenced when winsymlinks:native

[David Macek]

Can you describe what purpose does your C:\proc serve? I'm not currently 
arguing for or against Corinna's proposal, I'm just curious.

-- 
David Macek



smime.p7s
Description: S/MIME Cryptographic Signature

[PATCH] Add MacType to BLODA

[David Macek]

One more patch. MacType was observed by several users to cause `GPGME: Invalid 
crypto engine` failures in MSYS2. See 
.

I also removed two full stops in the sake of consistency.

* faq-using.xml: Add Forefront TMG to the BLODA

---
 winsup/doc/faq-using.xml | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/winsup/doc/faq-using.xml b/winsup/doc/faq-using.xml
index 35370f6..ae72145 100644
--- a/winsup/doc/faq-using.xml
+++ b/winsup/doc/faq-using.xml
@@ -1318,6 +1318,7 @@ behaviour which affect the operation of other programs, 
such as Cygwin.
 Citrix Metaframe Presentation Server/XenApp (see http://support.citrix.com/article/CTX107825;>Citrix Support 
page)
 Lavasoft Web Companion
 Forefront TMG
+MacType
 
 Sometimes these problems can be worked around, by temporarily or 
partially
 disabling the offending software.  For instance, it may be possible to disable
@@ -1332,7 +1333,7 @@ it may be necessary to uninstall the software altogether 
to restore normal opera
 Some of the symptoms you may experience are:
 
 
-Random fork() failures.
+Random fork() failures
 Caused by hook DLLs that load themselves into every process in the
 system.  POSIX fork() semantics require that the memory map of the child 
process
 must be an exact duplicate of the parent process' layout.  If one of these DLLs
@@ -1343,7 +1344,7 @@ DLL at that same address in the child, the fork() call 
has to fail.
 
 
 
-File access problems.
+File access problems
 Some programs (e.g., virus scanners with on-access scanning) scan or
 otherwise operate on every file accessed by all the other software running on
 your computer.  In some cases they may retain an open handle on the file even
-- 
2.6.2.windows.1

-- 
David Macek



smime.p7s
Description: S/MIME Cryptographic Signature