Re: getaddrinfo fails with EAI_NODATA for some valid hosts with A records

2016-01-10 Thread Brian Inglis
Andy Hall  comcast.net> writes:
>> On Jan  8 13:44, cyg Simple wrote:
>>> On 1/8/2016 6:14 AM, Corinna Vinschen wrote:
 $ ./gai leapsecond.utcd.org
 ret = 11004
 I have no idea why Windows' getaddrinfo chokes on leapsecond.utcd.org
 at all.
>>> utcd.org doesn't resolve for me.  So getaddrinfo has no info to get.
>> Why then does it work on Linux?
> nslookup works for me:
> Win7 64-bit
> $ nslookup leapsecond.utcd.org
> Non-authoritative answer:
> Server:  UnKnown
> Address:  192.168.1.1
> Name:leapsecond.utcd.org
> Address:  244.34.36.97
> Win10 64-bit
> C:\Users\Andy>nslookup leapsecond.utcd.org
> Server:  UnKnown
> Address:  192.168.1.1
> Non-authoritative answer:
> Name:leapsecond.utcd.org
> Address:  244.34.36.97
> However,  tracert and ping  yield this on both W7 & W10:
> $ tracert leapsecond.utcd.org
> Unable to resolve target system name leapsecond.utcd.org.
> $ tracert 244.34.36.97
> Tracing route to 244.34.36.97 over a maximum of 30 hops
>   1  Transmit error: code 1231.
> Trace complete.
> $ ping 244.34.36.97
> Pinging 244.34.36.97 with 32 bytes of data:
> PING: transmit failed. General failure.
> PING: transmit failed. General failure.
> PING: transmit failed. General failure.
> PING: transmit failed. General failure.
> Ping statistics for 244.34.36.97:
> Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
> Weird!

Everything works in my STC except Cygwin x86/x64 
"getent ahosts leapsecond.utcd.org" 
on Windows 7 x64 which uses Cygwin getaddrinfo. 
Windows getaddrinfo (ASCII names) in Corinna's STC; Cygwin getaddrinfo, and
Windows GetAddrInfoW (UCS2-LE names) used in the Cygwin implementations,
fail in my code. 
Identical code works from Linux via the same router, and Corinna's MinGW STC
indicates the problem is Windows code, not a BLODA, unless we define Windows
as a likely BLODA. ;^> 

Worked around the problem by falling back to trying gethostbyname when gai
returns 7 EAI_NODATA because GAIW returns 11004 WSANO_DATA. That error is
normally reported when there are no A (and/or , depending on family and
flags in the call) records for a domain name (most commonly only MX for mail
server, possibly CNAME misspelled or with missing associated A/, or
other DNS mis-configuration). 

Running whois utcd.org replies normally; whois, traceroute/tracert, and ping
all fail on the name and address as there is host at that address. 
The domain, name, address, SOA, NS, A, and PTR records were set up by P-HK
(phk.freebsd.dk) to provide leapsecond info from IERS Bulletin C encoded in
an address in the IP V4 global class E experimental 240/8 space, see code at
http://phk.freebsd.dk/time/20151122.html. 
An update is due next week for the end of June, when no change is expected,
except the date updated to be valid until after then. 



--
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: getaddrinfo fails with EAI_NODATA for some valid hosts with A records

2016-01-10 Thread Brian Inglis
Brian Inglis  SystematicSw.ab.ca> writes:
> Running whois utcd.org replies normally; whois, traceroute/tracert, and ping
> all fail on the name and address as there is host at that address. 

Running whois utcd.org replies normally; whois, traceroute/tracert, and ping
all fail on the name and address as there is *NO* host at that address.


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



Windows XP Support

2016-01-10 Thread Herbert Stocker

Hi,

i have read that beginning this month Cygwin wants to drop support
for Windows XP.  Though the home page and FAQ entry 12 do not talk
about this. Are they out of date or is WinXP still supported?

Although there are better OSes now, WinXP is still a good OS.
Especially for virtual machines, because of its low memory foot print.
Only just 220 MiB for the OS!

So while i feel it's not fair to beg you to go through all the
complexities of still supporting it, i want to ask:

- If there is no support anymore for Win XP (SP3), is there a reposi-
  tory around, where one can download the last version of Cygwin that
  supported WinXP (SP3)?

- If not, how can i do it by myself? Will i have to create a mirror
  and not update it? Or would i have to download the current version
  somehow?


Thank you very much for the great work.
Cygwin makes Windows complete if you ask me.

Herbert

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



After Windows 10 upgrade, SH fails "fork: can't reserve memory for parent stack"

2016-01-10 Thread Peter Binney
After Windows 10 upgraded itself from 10.0 (Build 10240) to 1511
(Build 10586) shell scripts fail with fork errors.

This can be demonstrated from a Cygwin64 Terminal window by running a
trivial pair of commands. Create these two files in a folder:

1.  win1511.pl containing the three lines:
my $subShell = "sh win1511.sh arg1 arg2";
print "Running: $subShell\n";
system("$subShell")

2.  win1511.sh containing the four lines:
#!/bin/bash
echo win1511.sh starts
sh -c "echo FROM SUBSHELL"# This fails under Windows (10) 1511
echo win1511 all done

Then change to the folder and run: perl win1511.pl

On a Windows 10 (10240) this reports, as expected:

Running: sh win1511.sh arg1 arg2
win1511.sh starts
FROM SUBSHELL
win1511 all done

But on the "upgraded" Windows, it reports something like:

Running: sh win1511.sh arg1 arg2
win1511.sh starts
  0 [main] sh 7208 C:\cygwin\bin\sh.exe: *** fatal error in
forked process - fork: can't reserve memory for parent stack 0x60
- 0x80, (child has 0x40 - 0x60), Win32 error 487
527 [main] sh 7208 cygwin_exception::open_stackdumpfile:
Dumping stack trace to sh.exe.stackdump
  0 [main] sh 1336 fork: child -1 - forked process 7208 died
unexpectedly, retry 0, exit code 0x100, errno 11
win1511.sh: fork: retry: No child processes
1011664 [main] sh 4084 C:\cygwin\bin\sh.exe: *** fatal error in
forked process - fork: can't reserve memory for parent stack 0x60
- 0x80, (child has 0x40 - 0x60), Win32 error 487
1012796 [main] sh 4084 cygwin_exception::open_stackdumpfile:
Dumping stack trace to sh.exe.stackdump
1055452 [main] sh 1336 fork: child -1 - forked process 4084 died
unexpectedly, retry 0, exit code 0x100, errno 11
win1511.sh: fork: retry: No child processes
3065101 [main] sh 1744 C:\cygwin\bin\sh.exe: *** fatal error in
forked process - fork: can't reserve memory for parent stack 0x60
- 0x80, (child has 0x40 - 0x60), Win32 error 487
3066077 [main] sh 1744 cygwin_exception::open_stackdumpfile:
Dumping stack trace to sh.exe.stackdump
3102454 [main] sh 1336 fork: child -1 - forked process 1744 died
unexpectedly, retry 0, exit code 0x100, errno 11
win1511.sh: fork: retry: No child processes
7111887 [main] sh 4100 C:\cygwin\bin\sh.exe: *** fatal error in
forked process - fork: can't reserve memory for parent stack 0x60
- 0x80, (child has 0x40 - 0x60), Win32 error 487
7112715 [main] sh 4100 cygwin_exception::open_stackdumpfile:
Dumping stack trace to sh.exe.stackdump
7152061 [main] sh 1336 fork: child -1 - forked process 4100 died
unexpectedly, retry 0, exit code 0x100, errno 11
win1511.sh: fork: retry: No child processes
15161677 [main] sh 1648 C:\cygwin\bin\sh.exe: *** fatal error in
forked process - fork: can't reserve memory for parent stack 0x60
- 0x80, (child has 0x40 - 0x60), Win32 error 487
15162561 [main] sh 1648 cygwin_exception::open_stackdumpfile:
Dumping stack trace to sh.exe.stackdump
15201626 [main] sh 1336 fork: child -1 - forked process 1648 died
unexpectedly, retry 0, exit code 0x100, errno 11
win1511.sh: fork: Resource temporarily unavailable


I am running the latest version (which I downloaded after the problem
started in case there was a fix already). uname -a reports:

CYGWIN_NT-10.0 JCPR-Dell-3 2.3.1(0.291/5/3) 2015-11-14 12:44 x86_64 Cygwin


I attach a cygcheck.out


cygcheck.out
Description: Binary 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: After Windows 10 upgrade, SH fails "fork: can't reserve memory for parent stack"

2016-01-10 Thread Achim Gratz
Peter Binney writes:
> I am running the latest version (which I downloaded after the problem
> started in case there was a fix already). uname -a reports:
>
> CYGWIN_NT-10.0 JCPR-Dell-3 2.3.1(0.291/5/3) 2015-11-14 12:44 x86_64 Cygwin

You'll want to install the latest test version (2.4.0-0.17).
https://cygwin.com/ml/cygwin/2016-01/msg00093.html


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

--
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: Windows XP Support

2016-01-10 Thread Terry McCarty - WA5NTI

Hello -

I am also new to the LINUX world and would like very much to see XP 
"live forever".


I still use XP as my main "go to" machine. 

But ... Microsoft's continuing "march to bigger and better" and my 
reluctance to be forced to repeatedly buy new bigger and faster 
machinery to accommodate the new windows systems has nudged me out of my 
complacency - I am now using Cygwin and learning LINUX.


If Cygwin continues to support XP, it will continue to serve as "that 
bright city on a hill", giving us old Microsoft Ludditess a comfortable 
"stepping stone" that encourages us to switch to LINUX.


--
Terry McCarty
   3...@comcast.net
   wa5nti



Herbert Stocker wrote:


Hi,

i have read that beginning this month Cygwin wants to drop support
for Windows XP.  Though the home page and FAQ entry 12 do not talk
about this. Are they out of date or is WinXP still supported?

Although there are better OSes now, WinXP is still a good OS.
Especially for virtual machines, because of its low memory foot print.
Only just 220 MiB for the OS!

So while i feel it's not fair to beg you to go through all the
complexities of still supporting it, i want to ask:

- If there is no support anymore for Win XP (SP3), is there a reposi-
  tory around, where one can download the last version of Cygwin that
  supported WinXP (SP3)?

- If not, how can i do it by myself? Will i have to create a mirror
  and not update it? Or would i have to download the current version
  somehow?


Thank you very much for the great work.
Cygwin makes Windows complete if you ask me.

Herbert

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




--
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: Windows XP Support

2016-01-10 Thread Juan Miguel Navarro Martínez
No software version can live forever, specially if it is a security
programs (OpenSSL, LibreSSL, GnuPG, ...) or programs and applications
that need the first ones, and that includes Operative Systems and Kernel.

And that's not a Microsoft thing, Linux as well has it.

Linux Kernel LTS support is 2-3 years, for Debian is 1 year after
release of next stable version, Ubuntu is 5 years and 9 months for STS
and both LinuxMint and Trisquel 5 years as well.

At least Windows XP got 13 years of support and since Windows Vista its
10 years.

On 2016-01-10 at 23:32, Terry McCarty - WA5NTI wrote:
> Hello -
> 
> I am also new to the LINUX world and would like very much to see XP
> "live forever".
> 
> I still use XP as my main "go to" machine.
> But ... Microsoft's continuing "march to bigger and better" and my
> reluctance to be forced to repeatedly buy new bigger and faster
> machinery to accommodate the new windows systems has nudged me out of my
> complacency - I am now using Cygwin and learning LINUX.
> 
> If Cygwin continues to support XP, it will continue to serve as "that
> bright city on a hill", giving us old Microsoft Ludditess a comfortable
> "stepping stone" that encourages us to switch to LINUX.
> 

-- 
Juan Miguel Navarro Martínez

GPG Keyfingerprint:
5A91 90D4 CF27 9D52 D62A
BC58 88E2 947F 9BC6 B3CF

--
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: Windows XP Support

2016-01-10 Thread Mike Brown
I've been using cygwin on XP (SP2 and then SP3), both 32 bit and 64 bit,
for ages now.  I actually tried upgrading once, but had to go back to what I
am currently running because cron was broken.  It refused to start, no matter
what.  After returning to the previous install, it started right up.

The main pieces that I use, zsh, cron and the basic commands (like ls and ps),
are all that I need.  I've written several z-shell scripts to do the things
that I need.

So, even if XP support is pulled, I'm good.

Cygwin has been really great for making the two XP boxes worth running.
I've been a Unix/Linux user/admin for decades.

MB

On Sun, Jan 10, 2016 at 05:32:21PM -0500, Terry McCarty - WA5NTI wrote:
> Hello -
>
> I am also new to the LINUX world and would like very much to see XP "live 
> forever".
>
> I still use XP as my main "go to" machine. 
> But ... Microsoft's continuing "march to bigger and better" and my 
> reluctance to be forced to repeatedly buy new bigger and faster machinery 
> to accommodate the new windows systems has nudged me out of my complacency 
> - I am now using Cygwin and learning LINUX.
>
> If Cygwin continues to support XP, it will continue to serve as "that 
> bright city on a hill", giving us old Microsoft Ludditess a comfortable 
> "stepping stone" that encourages us to switch to LINUX.
>
> -- 
> Terry McCarty
>3...@comcast.net
>wa5nti
>
>
>
> Herbert Stocker wrote:
>
>> Hi,
>>
>> i have read that beginning this month Cygwin wants to drop support
>> for Windows XP.  Though the home page and FAQ entry 12 do not talk
>> about this. Are they out of date or is WinXP still supported?
>>
>> Although there are better OSes now, WinXP is still a good OS.
>> Especially for virtual machines, because of its low memory foot print.
>> Only just 220 MiB for the OS!
>>
>> So while i feel it's not fair to beg you to go through all the
>> complexities of still supporting it, i want to ask:
>>
>> - If there is no support anymore for Win XP (SP3), is there a reposi-
>>   tory around, where one can download the last version of Cygwin that
>>   supported WinXP (SP3)?
>>
>> - If not, how can i do it by myself? Will i have to create a mirror
>>   and not update it? Or would i have to download the current version
>>   somehow?
>>
>>
>> Thank you very much for the great work.
>> Cygwin makes Windows complete if you ask me.
>>
>> Herbert
>>
>> -- 
>> 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
>>
>>
>
> --
> 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
>

-- 
e-mail: vid...@vidiot.com | vid...@vidiot.net/~\ The ASCII
6082066...@email.uscc.net (140 char limit)   \ / Ribbon Campaign
Visit - URL: http://vidiot.com/   X  Against
 http://vidiot.net/  / \ HTML Email
"What do you say Beckett. Wanna have a baby?" - Castle to Det. Beckett
"How long have I been gone?" Alexis after seeing Castle and Beckett w/ baby
 - Castle - 11/25/13

--
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: Question about incorrect System path from cygpath with case-sensitivity enabled

2016-01-10 Thread Bryan Henry
Hi Corinna,

Sorry for the delay getting back to you. I tested out the cygpath binary from 
the latest snapshot and confirmed that it fixes my issue. Thank for you making 
the change!

[~/Downloads/cygwin-inst-20160109]$ cygpath -W -u
/C/Windows
[~/Downloads/cygwin-inst-20160109]$ cygpath-old -W -u
/C/WINDOWS

- Bryan

> On Jan 7, 2016, at 3:19:38 PM, Corinna Vinschen  
> wrote:
> 
> On Jan  2 18:33, Andrey Repin wrote:
>> Greetings, Bryan Henry!
>> 
>>> I enabled (some time ago, not recently) case sensitivity on my Windows 8.1
>>> system by setting the registry key mentioned in the FAQ here:
>>> https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive
>> 
>>> Today, I updated Cygwin and noticed a message about a failed postinstall
>>> script at the end. Here's the excerpt from setup.log.full showing
>>> /etc/postinstall/base-files-mketc.sh exiting early:
>> 
>>> 2016/01/01 15:45:32 running: C:\cygwin\bin\bash.exe --norc --noprofile
>>> "/etc/postinstall/base-files-mketc.sh"
>>> Directory /C/WINDOWS/System32/drivers/etc does not exist; exiting
>>> If directory name is garbage you need to update your cygwin package
>>> 2016/01/01 15:45:32 abnormal exit: exit code=1
>> 
>>> Since this was an existing installation, that postinstall script failing
>>> isn't a big deal since the symlinks that it would normally create already
>>> exist, but I wanted to dig into why it's failing in the first place in case
>>> it is a symptom of something bigger. Taking a look at that script and trying
>>> "/usr/bin/cygpath -S -u" for myself, I see now why it failed:
>> 
>>> [~]$ cygpath -S -u
>>> /C/WINDOWS/System32
>>> [~]$ file `cygpath -S -u`
>>> /C/WINDOWS/System32: cannot open `/C/WINDOWS/System32' (No such file or 
>>> directory)
>>> [~]$ file /C/Windows/System32
>>> /C/Windows/System32: directory
>> 
>>> I get similar results from "cygpath -W". It seems that cygpath has not
>>> picked up on the fact that the directory is really "Windows" and not
>>> "WINDOWS",
>> 
>> cygpath uses system calls to return the directories you're asking for.
> 
> ...and those system calls return information which does not honor
> case-sensitivity, unfortunately.
> 
>> If a system call return wrong case, cygpath can't do anything to amend it.
> 
> It can and it will, at least if the path is a local path.  I just
> applied a patch to cygpath to call another OS function to correct the
> case of the path returned by GetSystemDirectory and friends.
> 
>> You have to fix your system first, then it will just work.
> 
> This is nonsense.  It's not the user's fault that the OS returns paths
> without honoring the case.  Cygwin tries to support case-sensitivity
> (https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive)
> and so it makes a lot of sense if cygpath tries to return system paths
> using the correct case.
> 
> I just uploaded new developer snapshots to https://cygwin.com/snapshots/
> Please give cygpath from those snapshots a try.
> 
> 
> Thanks,
> Corinna
> 
> -- 
> Corinna Vinschen  Please, send mails regarding Cygwin to
> Cygwin Maintainer cygwin AT cygwin DOT com
> Red Hat


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