Re: Problem with SSH log on through passwordless public key using the LSA security method on a Windows Server 2008 Standard machine

[Kent Larsson]

Hi again,

Has anyone got any idea on how to solve this? Do you know of *any*
Windows 2008 Server Standard Cygwin installation which is used as an
SSH-server where the users are able to login using a passwordless
public key? I'm beginning to suspect that it's just not possible with
this kind of Windows installation, which would be quite a problem.

Best and quite desperate regards,
Kent Larsson



2010/4/7 Kent Larsson :
> Hi,
>
> I'm having problems logging in to a Windows Server 2008 Standard
> machine using a password-less public key and I feel that I'm getting
> nowhere closer to solving it. Despite my attempts the log in always
> results in asking for my account password. Logging in using a password
> works well, but I really need to log in using my public.
>
> What I've done is:
>  1. Turing DEP off by: bcdedit.exe /set {current} nx AlwaysOff
>  2. Installing Cygwin
>  3. Execute /usr/bin/cyglsa-config to use "Switching the user context
> without password, Method 2: LSA authentication package" from
> http://cygwin.com/cygwin-ug-net/ntsec.html followed by a computer
> restart
>  4. Added the row "CYGWIN=binmode tty ntsec" (without ") to
> c:\cygwin\Cygwin.bat
>  5. Execute "ssh-host-config" choosing the defaults, I wrote "binmode
> tty ntsec" when asked for the CYGWIN contents
>
> After that, the system has been restarted numerous times. I also have
> "Cron deamon" running, under a domain account. But I don't think it
> affects the issue. I'm able to log in using a password, but not using
> a public key. Also the su command doesn't work, it asks me for a
> password when issuing it and always respons with "su: /bin/bash:
> Permission denied", that one might be related?
>
> Below are some output which might make it easier to know what's wrong
> divided into ** headlines **.
>
> Thank you for reading! I hope someone has a tip or two. Any help is
> greatly appreciated! :-)
>
> Best regards,
> Kent Larsson
>
> ** bcdedit.exe **
>
> C:\Users\netdevel>bcdedit.exe
>
> Windows Boot Manager
> 
> identifier              {bootmgr}
> device                  partition=C:
> description             Windows Boot Manager
> locale                  en-US
> inherit                 {globalsettings}
> default                 {current}
> displayorder            {current}
> toolsdisplayorder       {memdiag}
> timeout                 30
> resume                  No
>
> Windows Boot Loader
> ---
> identifier              {current}
> device                  partition=C:
> path                    \Windows\system32\winload.exe
> description             Microsoft Windows Server 2008
> locale                  en-US
> inherit                 {bootloadersettings}
> osdevice                partition=C:
> systemroot              \Windows
> resumeobject            {13f36e53-1fe7-11df-8fce-99bbadfdd430}
> nx                      AlwaysOff
>
> ** The ssh-host-config script and some thoughts **
>
> /usr/share/doc/Cygwin/openssh.README says:
> 1. The user which runs the "CYGWIN sshd"-service should have the rights:
>  a. "Create a token object"
>  b. "Logon as a service"
>  c. "Replace a process level token"
>  d. "Increase Quota"
> 2. The "ssh-host-config" script asks you, if it should create such an
> account, called "sshd_server" with the correct (above) rights.
> 3. Note that ssh-user-config sets the permissions on 2003 Server
> machines dependent of whether a sshd_server account exists or not.
>
> I don't understand [3] above and [2] doesn't seem to be quite right
> any more? As far as I can tell, when I ran the script and an account
> named "cyg_server" was created. The "CYGWIN sshd"-service is running
> under the created account.
>
> By logging on to the server and "Start / Administrative Tools / Local
> Security Policy / Local Policies / User Rights Assignment" I'm able to
> verify that the "cyg_server" which runs the "CYGWIN sshd"-service has
> the 1a,1b,1c rights. But the 1d (Increase Quota) can not be found
> under "User Rights Assignment". The two who start with "Increase" are
> "Increase a process working set" and "Increase scheduling priority".
> Neither of which the "cyg_server" account is assigned.
>
> What's different from the README above is the account name, and maybe
> the lack of "Increase Quota" (I have no idea where I should be able to
> find it if not where I looked, and if it really is necessary).
>
> ** Cygwin version **
>
> $ uname -a
> CYGWIN_NT-6.0 kentl 1.7.1(0.218/5/3) 2009-12-07 11:48 i686 Cygwin
>
> ** Installed Cygwin packages **
>
> $ cygcheck -c
> Cygwin Package Information
> Package              Version             Status
> _update-info-dir     00871-1             OK
> alternatives         1.3.30c-10          OK
> arj                  3.10.22-1           OK
> aspell               0.60.5-1            OK
> aspell-en            6.0.0-1             OK
> aspell-sv            0.50.2-2            OK
> autossh              1.4b-1              OK
> base-cygwin          2.1-1    

Re: 1.7.3: Backspace key not working in GNU screen.

[Andy Koppe]

Al G.:
> using GNU screen (4.00.03) and trying to backspace by
> hitting the backspace key results in nothing happening. The cursor
> doesn't move, the character isn't erased and the command remains the
> same (if you hit Enter whatever your typo was gets the usual error).

Uh oh, this is most likely due to the change for allowing the
backspace keycode to be set using 'stty erase' (which I'd suggested).
I can reproduce the problem from 1.7.2 onwards. The backspace key is
sending ^@ (i.e. 0x00), same as previously happened with CYGWIN=tty in
1.7.1 snapshots. So it looks like the termios structure that the
keyboard handling reads isn't getting initialised in this case.

Workarounds: Add 'set CYGWIN=tty' to Cygwin.bat (or wherever you're
starting your session from), or use one of the other terminals.

Andy

--
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: man pages showing special characters

[Andy Koppe]

On 8 April 2010 21:56, Paul Bibbings:
>> What font are you using, and what do you get instead of the '-'?
>
> Well, certainly the font affects the problem.  I had this set to
> `Courier'.  However, changing this to `Courier New' solves this for me
> and everything renders as I would expect.  For the record, using
> `Courier', I was getting a wide, solid vertical bar for al the `-'s.

The font *is* the problem then. Well, apart from man/groff needlessly
using the Unicode minus and hyphen codepoints anyway. 'Courier' isn't
a Unicode font, i.e. it covers CP1252 and perhaps a few other
codepages, but nothing beyond that.

Other examples of fonts like that are Fixedsys and Terminal. OpenType
and TrueType fonts (marked with 'O' and 'TT' in the font dialog) tend
to have wider coverage, for example Lucida Console, Consolas, DejaVu
Mono, and Courier New.


> I had believed that I had set it to `Courier New' in the first place, so
> unless it should render properly under Courier, this is my error.

Easy enough to click on 'Courier' instead of 'Courier New'. I checked
that mintty isn't accidentally dropping the 'New'.

Andy

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

Opa

[Bryan Karsh]

http://mahour.com/HNravqOJ2r.htm

--
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: Problem with SSH log on through passwordless public key using the LSA security method on a Windows Server 2008 Standard machine

[Corinna Vinschen]

On Apr 10 11:09, Kent Larsson wrote:
> Hi again,
> 
> Has anyone got any idea on how to solve this? Do you know of *any*
> Windows 2008 Server Standard Cygwin installation which is used as an
> SSH-server where the users are able to login using a passwordless
> public key? I'm beginning to suspect that it's just not possible with

Mine, for instance.  We also have customers using SSH on 2008.

> 2010/4/7 Kent Larsson :
> > Hi,
> >
> > I'm having problems logging in to a Windows Server 2008 Standard
> > machine using a password-less public key and I feel that I'm getting
> > nowhere closer to solving it. Despite my attempts the log in always
> > results in asking for my account password. Logging in using a password
> > works well, but I really need to log in using my public.
> >
> > What I've done is:
> >  1. Turing DEP off by: bcdedit.exe /set {current} nx AlwaysOff

Not necessary.  Mine's running with "DEP for all programs" just fine.

> >  2. Installing Cygwin
> >  3. Execute /usr/bin/cyglsa-config to use "Switching the user context
> > without password, Method 2: LSA authentication package" from
> > http://cygwin.com/cygwin-ug-net/ntsec.html followed by a computer
> > restart
> >  4. Added the row "CYGWIN=binmode tty ntsec" (without ") to
> > c:\cygwin\Cygwin.bat

Huh?  http://cygwin.com/cygwin-ug-net/using-cygwinenv.html

> >  5. Execute "ssh-host-config" choosing the defaults, I wrote "binmode
> > tty ntsec" when asked for the CYGWIN contents

Again, http://cygwin.com/cygwin-ug-net/using-cygwinenv.html

Neither of these makes sense.

> > After that, the system has been restarted numerous times. I also have
> > "Cron deamon" running, under a domain account. But I don't think it
> > affects the issue. I'm able to log in using a password, but not using
> > a public key. Also the su command doesn't work, it asks me for a
> > password when issuing it and always respons with "su: /bin/bash:
> > Permission denied", that one might be related?

http://www.cygwin.com/faq/faq.using.html#faq.using.su

And maybe that helps:

http://www.cygwin.com/faq/faq.using.html#faq.using.sshd-in-domain


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  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

DBD-DB2-1.78 driver for Perl V5.10 under CYGWIN 1.7.4

[ERIC HO]

Just wondering if anyone has successfully installed DBD-DB2-1.78 driver
for Perl V5.10 under CYGWIN 1.7.4 successfully. Please let me know the 
changes required to install it. Thanks.

Regards,

Eric

--
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: 1.7.3: Backspace key not working in GNU screen.

[Christopher Faylor]

On Sat, Apr 10, 2010 at 10:31:36AM +0100, Andy Koppe wrote:
>Workarounds: Add 'set CYGWIN=tty' to Cygwin.bat (or wherever you're
>starting your session from), or use one of the other terminals.

If setting CYGWIN=tty affects the setting of the backspace key for ptys
then that's a bug in Cygwin.  You really should *not* be setting
CYGWIN=tty for applications like mintty, rxvt, xterm, ssh, screen, etc.,
which use ptys.  Really.

cgf

--
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: less-436-1

[Christopher Faylor]

I've made a new version of less available for installation.  This is the
most recent version of less available from greenwoodsoftware.com.  The
description of what's new from the last release is below.

  *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, please
use the automated form at:

http://cygwin.com/lists.html#subscribe-unsubscribe

If this does not work, then 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@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.


  * Excerpted from the less NEWS file *


 NEWS about less

==

  For the latest news about less, see the "less" Web page:
  http://www.greenwoodsoftware.com/less
  You can also download the latest version of less from there.

  To report bugs, suggestions or comments, send email to
  bug-l...@gnu.org or ma...@greenwoodsoftware.com.

==

Major changes between "less" versions 429 and 436

* Don't pass "-" to non-pipe LESSOPEN unless it starts with "-".

* Allow a fraction as the argument to the -# (--shift) option.

* Fix highlight bug when underlined/overstruck text matches at end of line.

* Fix non-regex searches with ctrl-R.

--
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.19.51-2

[Christopher Faylor]

I've made a new version of binutils available for installation.  This is
a refresh against the current CVS.

A partial list of changes is included after the unsubscribe info.  This list
comes from three binutils NEWS files.

  *** 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@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 the above URL.



* * * *

* Add support for delay importing to dlltool.  Use the --output-delaylib 
   switch to create a delay-import library.  The resulting app will load the dll
   as soon as the first function is called.  It will link to 
__delayLoadHelper2()
   from the static delayimp library, which will import LoadLibraryA and
   GetProcAddress from kernel32.

* Extend .def file syntax by '== ' for imports and exports. This allows
  to alias the import/export table name written in PE image.

* Add --exclude-all-symbols option to PE based linkers.  This prevents all
  symbols from automatically being exported.

* Improvements in pseudo-reloc for PE targets.

--
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: byacc-20100216-1

[Christopher Faylor]

I've made a new version of 'byacc' available for installation.  This
is the most recent version of byacc available from Thomas Dickey's "fork"
of the codebase which includes many fixes and modernizations.  A list of
new features gleaned from the ChangeLog is included after the unsubscribe
info.

  *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, please
use the automated form at:

http://cygwin.com/lists.html#subscribe-unsubscribe

If this does not work, then 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@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.

* * * *

New Features:

- Improved yacc man page.

- Implement %pure-parser.

- Fix a memory leak in the generated skeleton.

--
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: bison-2.4.2-1

[Christopher Faylor]

I've made a new version of 'bison' available for download.  This updates
the package to the latest version available from ftp.gnu.org.  I've included
the relevant portions of the Bison NEWS file at the end of this message.

For a brief description of this package, see http://cygwin.com/packages/ .

To update your installation, click on the "Install Cygwin now" link on
the http://cygwin.com/ web page.  This downloads setup.exe to your
system.  Run setup.exe to install or update the bison package.

If you have questions or comments, please send them to the Cygwin
mailing list.  I would appreciate it if you would use the mailing list
rather than emailing me directly.

  *** 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@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 the above URL.

Bison News
--

* Changes in version 2.4.2 (2010-03-20):

** Some portability problems that resulted in failures and livelocks
   in the test suite on some versions of at least Solaris, AIX, HP-UX,
   RHEL4, and Tru64 have been addressed.  As a result, fatal Bison
   errors should no longer cause M4 to report a broken pipe on the
   affected platforms.

** `%prec IDENTIFIER' requires IDENTIFIER to be defined separately.

  POSIX specifies that an error be reported for any identifier that does
  not appear on the LHS of a grammar rule and that is not defined by
  %token, %left, %right, or %nonassoc.  Bison 2.3b and later lost this
  error report for the case when an identifier appears only after a
  %prec directive.  It is now restored.  However, for backward
  compatibility with recent Bison releases, it is only a warning for
  now.  In Bison 2.5 and later, it will return to being an error.

** Detection of GNU M4 1.4.6 or newer during configure is improved.

** Warnings from gcc's -Wundef option about undefined YYENABLE_NLS,
   YYLTYPE_IS_TRIVIAL, and __STRICT_ANSI__ in C/C++ parsers are now
   avoided.

** %code is now a permanent feature.

  A traditional Yacc prologue directive is written in the form:

%{CODE%}

  To provide a more flexible alternative, Bison 2.3b introduced the
  %code directive with the following forms for C/C++:

%code  {CODE}
%code requires {CODE}
%code provides {CODE}
%code top  {CODE}

  These forms are now considered permanent features of Bison.  See the
  %code entries in the section "Bison Declaration Summary" in the Bison
  manual for a summary of their functionality.  See the section
  "Prologue Alternatives" for a detailed discussion including the
  advantages of %code over the traditional Yacc prologue directive.

  Bison's Java feature as a whole including its current usage of %code
  is still considered experimental.

** YYFAIL is deprecated and will eventually be removed.

  YYFAIL has existed for many years as an undocumented feature of
  deterministic parsers in C generated by Bison.  Previously, it was
  documented for Bison's experimental Java parsers.  YYFAIL is no longer
  documented for Java parsers and is formally deprecated in both cases.
  Users are strongly encouraged to migrate to YYERROR, which is
  specified by POSIX.

  Like YYERROR, you can invoke YYFAIL from a semantic action in order to
  induce a syntax error.  The most obvious difference from YYERROR is
  that YYFAIL will automatically invoke yyerror to report the syntax
  error so that you don't have to.  However, there are several other
  subtle differences between YYERROR and YYFAIL, and YYFAIL suffers from
  inherent flaws when %error-verbose or `#define YYERROR_VERBOSE' is
  used.  For a more detailed discussion, see:

http://lists.gnu.org/archive/html/bison-patches/2009-12/msg00024.html

  The upcoming Bison 2.5 will remove YYFAIL from Java parsers, but
  deterministic parsers in C will continue to implement it.  However,
  because YYFAIL is already flawed, it seems futile to try to make new
  Bison features compatible with it.  Thus, during parser generation,
  Bison 2.5 will produce a warning whenever it discovers YYFAIL in a
  rule action.  In a later release, YYFAIL will be disabled for
  %error-verbose and `#define YYERROR_VERBOSE'.  Eventually, YYFAIL will
  be removed altogether.

  There exists at least one case where Bison 2.5's YYFAIL warning will
  be a false positive.  Some projects add phony uses of YYFAIL and other
  Bison-defined macros for the sole purpose of suppressing C
  preprocessor warnings (from GCC cpp's -Wunused-macros, for example).
  To avoid Bison's future warning, such YYFAIL uses can be moved to the
  epilogue (that is, after

Re: 1.7.3: Backspace key not working in GNU screen.

[Andy Koppe]

Christopher Faylor:
>>Workarounds: Add 'set CYGWIN=tty' to Cygwin.bat (or wherever you're
>>starting your session from), or use one of the other terminals.
>
> If setting CYGWIN=tty affects the setting of the backspace key for ptys
> then that's a bug in Cygwin.  You really should *not* be setting
> CYGWIN=tty for applications like mintty, rxvt, xterm, ssh, screen, etc.,
> which use ptys.  Really.

The issue only affects the specific case of 'screen' running in the
console without 'tty' in the CYGWIN settings: the backspace key sends
^@ instead of what's set in the console's stty settings. Yes, I assume
it's a Cygwin bug.

Andy

--
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: 1.7.4: Building Xalan-C results in a unusable library

[Dave Korn]

On 10/04/2010 11:36, Reto Schneider wrote:

>> make DESTDIR=/.. install (just "make install" would result in a failing 
>> "mkdir -p //usr/local/lib"
> call)

  Heh.  That's a very common minor bug in automake-based makefiles that has no
consequences on Linux, but fails nastily on Windows.  The POSIX spec says that
"//" at the beginning of a file path can be reserved for special meanings by
the system; Linux doesn't take advantage of this leeway, and just treats it as
a null path component, but on Cygwin it was the ideal place to add support for
windows-style UNC paths.

  The bug will be because they've written "$(DESTDIR)/$(prefix)" somewhere in
a makefile; there shouldn't be a separator, destdir should always have a
trailing one when non-empty, and the construct should just be written
"$(DESTDIR)$(prefix)".

> Now the strange part:

> To me it looks as if this file is broken:
> 
> $ ldd /usr/local/lib/cygxalan-c111.dll
>   ntdll.dll => /cygdrive/c/Windows/SysWOW64/ntdll.dll (0x7705)
>   kernel32.dll => /cygdrive/c/Windows/syswow64/kernel32.dll (0x76b5)
>   KERNELBASE.dll => /cygdrive/c/Windows/syswow64/KERNELBASE.dll 
> (0x7505)
>   ??? => ??? (0x6dcc)
> 
> All the other dll-files (eg. under /usr/bin/ or /usr/local/bin (have a recent 
> boost installed here)
> ) do not have this suspicions ???.

  That's really peculiar.  Something may have gone bizarrely wrong during the
build.  Do you have a log file?  If so, upload it to pastebin.org or somewhere
like that, post the URL to the list and I'll take a look and see if I can spot
anything unusual.

cheers,
  DaveK


--
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: 1.7.3: Backspace key not working in GNU screen.

[Christopher Faylor]

On Sat, Apr 10, 2010 at 05:00:30PM +0100, Andy Koppe wrote:
>Christopher Faylor:
>>>Workarounds: Add 'set CYGWIN=tty' to Cygwin.bat (or wherever you're
>>>starting your session from), or use one of the other terminals.
>>If setting CYGWIN=tty affects the setting of the backspace key for ptys
>>then that's a bug in Cygwin.  ??You really should *not* be setting
>>CYGWIN=tty for applications like mintty, rxvt, xterm, ssh, screen,
>>etc., which use ptys.  ??Really.
>
>The issue only affects the specific case of 'screen' running in the
>console without 'tty' in the CYGWIN settings: the backspace key sends
>^@ instead of what's set in the console's stty settings.  Yes, I assume
>it's a Cygwin bug.

Since setting CYGWIN=tty is pretty much equivalent to running under a
pty I'd say that it could actually be a screen bug.

Regardless, I hate for this to become entrenched in Cygwin lore.
Setting CYGWIN=tty should not be viewed as a solution and I want to make
very sure that the archives reflect that.

cgf

--
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: abnormal exit: exit code=-1073741795

[Dave Korn]

On 09/04/2010 14:52, Stephen Grant Brown wrote:

> I have two versions of cygwin setup on my computer. One is
> cygwin-legacy, the other is a install of the latest cygwin software.
> 
> Both "bash.exe --version" and "cp --version"  when run from the latest
> cygwin return the above exit code and produce no output.
> 
> cygwin-legacy runs normally.
> 
> Please find attaached output from cygwin-legacy's "chkcheck -svr >
> cygwin.out"
> 
> What does the above exit code mean?

  In hexadecimal, it's 0xC01D, which is the NTSTATUS error code for
"STATUS_ILLEGAL_INSTRUCTION".  Cygwin 1.7 requires at least an i686 level cpu,
with full support for SSE/MMX; what processor do you have in your machine?  Is
it one of the limited Cyrix CPUs that don't support all the i686 feature set?

> How do I compile bash under cygwin?

  To recompile any existing Cygwin package, use setup.exe in "install from
internet" mode, and select the 'Src' checkbox next to the package you want.
That will download and install the sources, including any cygwin-specific
patches needed, into your /usr/src directory.

  What happens next depends on the package; some of them supply a shell script
(*.sh) that correctly unpacks, patches, configures and builds the sources;
other packages will come with a *.cygport script which is processed by the
"cygport" utility to perform the same set of tasks.  A few might come with no
build script of any kind at all, in which case the standard "./configure &&
make all && make install" technique should work.

> What is a good reference to learn c++?

  Hard to say, since it depends what style suits your personal learning
preferences best.  The obvious reference is Stroustrup's own book about it:

http://www2.research.att.com/~bs/3rd.html

cheers,
  DaveK


--
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: 1.7.3: Backspace key not working in GNU screen.

[Christopher Faylor]

On Sat, Apr 10, 2010 at 12:16:26PM -0400, Christopher Faylor wrote:
>On Sat, Apr 10, 2010 at 05:00:30PM +0100, Andy Koppe wrote:
>>The issue only affects the specific case of 'screen' running in the
>>console without 'tty' in the CYGWIN settings: the backspace key sends
>>^@ instead of what's set in the console's stty settings.  Yes, I assume
>>it's a Cygwin bug.
>
>Since setting CYGWIN=tty is pretty much equivalent to running under a
>pty I'd say that it could actually be a screen bug.

Nope, you're right.  It's a Cygwin bug.  I'm fixing it now.

cgf

--
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: 1.7.3: Backspace key not working in GNU screen.

[Christopher Faylor]

On Sat, Apr 10, 2010 at 01:36:07PM -0400, Christopher Faylor wrote:
>On Sat, Apr 10, 2010 at 12:16:26PM -0400, Christopher Faylor wrote:
>>On Sat, Apr 10, 2010 at 05:00:30PM +0100, Andy Koppe wrote:
>>>The issue only affects the specific case of 'screen' running in the
>>>console without 'tty' in the CYGWIN settings: the backspace key sends
>>>^@ instead of what's set in the console's stty settings.  Yes, I assume
>>>it's a Cygwin bug.
>>
>>Since setting CYGWIN=tty is pretty much equivalent to running under a
>>pty I'd say that it could actually be a screen bug.
>
>Nope, you're right.  It's a Cygwin bug.  I'm fixing it now.

I'm not 100% sure that this is the right fix but the new snapshot at
least works around the problem.

The problem is that screen explicitly sets VERASE to 0.  I believe that
it does that to mean "there is really no erase character since I'm
handling that".  That should not cause Cygwin to send a null character.
I think it should probably just send the default \177 character.

So that is the change I've made.

cgf

--
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: diffutils-2.9-1

[Christopher Faylor]

I've made a new version of 'diffutils' (http://www.gnu.org/software/diffutils/)
available for installation.  This is the most recent version of diffutils from
ftp.gnu.org .  I've included a snippet from the diffutils NEWS after the
unsubscribe info.

  *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, please
use the automated form at:

http://cygwin.com/lists.html#subscribe-unsubscribe

If this does not work, then 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@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.

* * *
GNU diffutils NEWS-*- outline -*-

* Noteworthy changes in release 2.9 (2010-02-11) [stable]

** New features

  New diff option --suppress-blank-empty.

  Bring back support for `diff -NUM', where NUM is a number,
  even when conforming to POSIX 1003.1-2001.  This change reverts to
  the behavior of GNU diff 2.7 and earlier.  This is a change only
  when conforming to POSIX 1003.1-2001; there is no effect when
  conforming to older POSIX versions.

  This change is in response to decisions taken in the January 2005
  Austin Group standardization meeting.  For more details, please see
  "Utility Syntax Guidelines" in the Minutes of the January 2005
  Meeting .

  sdiff now understands '1' and '2' as synonyms for 'l' and 'r'.

** Changes in behavior

  sdiff and diff3 now invoke diff, not $(bindir)/diff


--
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: 1.7.4: Building Xalan-C results in a unusable library

[Dave Korn]

On 10/04/2010 11:36, Reto Schneider wrote:

> I'm doing the following steps:

  So, I quickly checked out the sources and tried your build recipe, realised
I needed to install xerces-devel, did so, finished the build and installed.

> Now the strange part:
> 
> $ /usr/local/bin/Xalan.exe
> /usr/local/bin/Xalan.exe: error while loading shared libraries: 
> cygxalan-c111.dll: cannot open
> shared object file: No such file or directory

  Ah, the message is confusing.  It is not cygxalan-c111.dll that cannot be
found, but a library to which it is linked that cannot be found, preventing
cygxalan-c111.dll from being loaded by Xalan.exe.

> To me it looks as if this file is broken:
> 
> $ ldd /usr/local/lib/cygxalan-c111.dll

  Hmm, I don't know what ldd is doing, but I used cygcheck to take a look at it:

> $ PATH=/tmp/xalan/install/usr/local/bin:$PATH  cygcheck  
> ./usr/local/bin/Xalan.
> exe
> F:\cygwin-1.7\tmp\xalan\install\usr\local\bin\Xalan.exe
>   F:\cygwin-1.7\bin\cygwin1.dll
> C:\WINNT\system32\ADVAPI32.DLL
>   C:\WINNT\system32\KERNEL32.dll
> C:\WINNT\system32\ntdll.dll
>   C:\WINNT\system32\RPCRT4.dll
>   F:\cygwin-1.7\bin\cygxerces-c-3-0.dll
> F:\cygwin-1.7\bin\cyggcc_s-1.dll
> F:\cygwin-1.7\bin\cygstdc++-6.dll
> F:\cygwin-1.7\bin\cygcurl-4.dll
>   F:\cygwin-1.7\bin\cygcrypto-0.9.8.dll
>   F:\cygwin-1.7\bin\cygidn-11.dll
> F:\cygwin-1.7\bin\cygiconv-2.dll
> F:\cygwin-1.7\bin\cygintl-8.dll
>   F:\cygwin-1.7\bin\cygssh2-1.dll
> F:\cygwin-1.7\bin\cygz.dll
>   F:\cygwin-1.7\bin\cygssl-0.9.8.dll
> F:\cygwin-1.7\bin\cygicuuc38.dll
>   F:\cygwin-1.7\bin\cygicudata38.dll
>   F:\cygwin-1.7\tmp\xalan\install\usr\local\bin\cygxalan-c111.dll
> cygcheck: track_down: could not find cygxalanMsg111.dll

  So, it turns out there's a bug in the "make install" stage.  The missing
cygxalanMsg111.dll is built OK, but only the link library gets installed, not
the actual DLL itself.  You need to talk to upstream about this bug in their
makefile.  As a workaround, copying the DLL manually from the build directory
to whereever you've got the other DLL installed works fine.

cheers,
  DaveK


--
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: 1.7.4: Building Xalan-C results in a unusable library

[Reto Schneider]

Dave Korn wrote:
>   Ah, the message is confusing.  It is not cygxalan-c111.dll that cannot be
> found, but a library to which it is linked that cannot be found, preventing
> cygxalan-c111.dll from being loaded by Xalan.exe.

First: I'm really sorry for not telling you that I solved the problem in the 
meantime. (train does
not wait :( )

Thank you a lot for your help, it was exactly this issue. I found this when I 
got some help in
#cygwin at freenode.

I'll report the two problems to the xalan devs.

Regards,
Reto

--
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: 1.7.3: Backspace key not working in GNU screen.

[Andy Koppe]

Christopher Faylor wrote:
> I'm not 100% sure that this is the right fix but the new snapshot at
> least works around the problem.

Thanks.

> The problem is that screen explicitly sets VERASE to 0.  I believe that
> it does that to mean "there is really no erase character since I'm
> handling that".

You're right. Zero is the value of the _POSIX_VDISABLE constant for
disabling special characters. Therefore, using c_cc[VERASE] as the
backspace keycode was a bad idea all along. Sorry for suggesting it in
the first place.

> That should not cause Cygwin to send a null character.
> I think it should probably just send the default \177 character.

Makes sense given the botched design, but of course it does mean that
the user's backspace keycode setting is ignored. Also, 'screen' would
be expecting what was set in c_cc[VERASE] as the backspace keycode.

I can think of two ways to fix the design. One would be to introduce a
CYGWIN flag for switching from the default ^? to ^H, named something
like 'backspace_sends_bs', 'legacy_bs' or 'bs_is_ctrl_h'. Another
would be to implement the DECBKM ("DEC Backarrow Key Mode") control
sequence for the purpose, which is also supported by xterm and mintty:

\e[?67h  Backspace key sends ^H
\e[?67l  Backspace key sends ^?

Andy

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

Setup displays wrong version

[NightStrike]

When you run setup on a clean system, there's an alert that warns you
if this is your first time installing cygwin.  It says "This is the
first time you've installed cygwin 1.7.1."  I'm guessing this version
number should either say 1.7, or should be otherwise handled
differently.

--
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: [ANNOUNCEMENT] Updated: binutils-2.19.51-2

[Angelo Graziosi]

Christopher Faylor wrote:

I've made a new version of binutils available for installation.


Pheraps there was some problem in uploading... It seem that the new 
package is on the mirrors (at least on mirrors.kernel.org), but not in 
setup.ini. This happens since a few hours. No problems with the other 
package announced today.


Thanks,
Angelo.

--
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: 1.7.4: Building Xalan-C results in a unusable library

[Dave Korn]

On 10/04/2010 20:21, Reto Schneider wrote:
> Dave Korn wrote:
>>   Ah, the message is confusing.  It is not cygxalan-c111.dll that cannot be
>> found, but a library to which it is linked that cannot be found, preventing
>> cygxalan-c111.dll from being loaded by Xalan.exe.
> 
> First: I'm really sorry for not telling you that I solved the problem in the 
> meantime. (train does
> not wait :( )

  That's ok; because you gave me the exact command lines to reproduce the
problem, it was really no trouble at all to cut and paste them into a spare
bash shell and leave a build running in the background while I got on with
other stuff.

cheers,
  DaveK


--
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: Xcompose like input for UTF-8 ?

[Rurik Christiansen]

On 10/04/2010 12:11 AM, Thomas Wolff wrote:
> On 05.04.2010 09:46, Rurik Christiansen wrote:
>> On 5/04/2010 5:59 AM, Andy Koppe wrote:
>>   
>>> Rurik Christiansen wrote:
>>>
>>> 
 Is there a way to have something similar to Xcompose for utf8 input
 ?   
>>> You can have actual Xcompose by running an X server and using xterm or
>>> rxvt-unicode.

How do I enable that ? (doesn't work by default)
  
> Do you need it throughout in the shell/terminal or would it be
> sufficient to have it in an editor?

Ideally universally. But I am using it mostly in email, zim (personal
wiki type app), vim and CLI
(ok, in vim I can use the digraphs but an unified interface would be ideal)

For a while I looked at autohotkey but is not as straightforward as I
thought (even if I still think is the best shot).

> You might give mined a try; it has built-in support for a variety of
> convenient input support methods,
> for example you can type Control-comma c and will get a c with cedilla
> (works in xterm and mintty).

Ah yes thanls for the suggestion :) ... I'm already familiar with vi so
I may stick with it in the mean time

Cheers

-- 
Nothing is true. Everything is permitted.


--
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: How to uninstall Cygwin/X (only)

[Norton Allen]

On 4/9/2010 5:56 AM, Paul Bibbings wrote:
> If by "add a right-click context menu to the spinner" you intend to
> retain the current problematic behaviour of the spinner but add the
> context menu by way of avoiding the noted problems of cycling through
> `uninstall', then I would, as a user, see that as an inconsistency.  I
> would expect the two to be alternative ways of achieving the same thing
> and regard the (presumably) silent difference to be a design flaw.  I may
> be missing something, but I'm wondering how it is that, if the pass
> through `install' can put in all the dependencies, continuing to
> `uninstall' can't just take them out again?
>   
So what you want setup to do is remember whether a package was selected
by the user or simply included to satisfy a dependency. Then when a
package is deselected, the dependencies can be reevaluated.


--
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: 1.7.3: Backspace key not working in GNU screen.

[Christopher Faylor]

On Sat, Apr 10, 2010 at 10:09:32PM +0100, Andy Koppe wrote:
>Christopher Faylor wrote:
>> That should not cause Cygwin to send a null character.
>> I think it should probably just send the default \177 character.
>
>Makes sense given the botched design, but of course it does mean that
>the user's backspace keycode setting is ignored. Also, 'screen' would
>be expecting what was set in c_cc[VERASE] as the backspace keycode.

Uh, no.  I made it send \177 when c_cc[VERASE] is 0.  Screen is just
forwarding characters along so it doesn't care.

cgf

--
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: How to uninstall Cygwin/X (only)

[Paul Bibbings]

Norton Allen  writes:

> On 4/9/2010 5:56 AM, Paul Bibbings wrote:
>> If by "add a right-click context menu to the spinner" you intend to
>> retain the current problematic behaviour of the spinner but add the
>> context menu by way of avoiding the noted problems of cycling through
>> `uninstall', then I would, as a user, see that as an inconsistency.  I
>> would expect the two to be alternative ways of achieving the same thing
>> and regard the (presumably) silent difference to be a design flaw.  I may
>> be missing something, but I'm wondering how it is that, if the pass
>> through `install' can put in all the dependencies, continuing to
>> `uninstall' can't just take them out again?
>>   
> So what you want setup to do is remember whether a package was selected
> by the user or simply included to satisfy a dependency. Then when a
> package is deselected, the dependencies can be reevaluated.

Although I hadn't considered it fully when I wrote the above, this idea
certainly emerged as one that addresses a valid use case, the more I
thought about it.  Having said that, the more that I /have/ thought
about it, the more the set of valid use-cases seems to grow and the
whole thing starts to look horribly complex. Not that I'm wanting to
suggest that all `valid' (whatever that means) use cases /should/ be
accommodated. Like any maintenance project, if no-one's asking for it,
don't add it.

On a related note, it does seem that the current implementation is quite
geared towards the user simply making choices and then proceeding
straight to next. It's when a user changes their mind, or performs other
actions before proceeding to next that issues seem to arise.  For
instance, if I click on the view button and select `Not installed',
suppose I select a package that I don't have - for example (I'm trying
this now), aspell-dev 0.60.5-1.  Then, suppose I merely cycle through
the Views and come back to `Not installed'. aspell-dev is no longer in
the list, despite the fact that I have not done anything other than
change the view.  It is no more installed now than it was before. 

Regards

Paul Bibbings


--
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: How to uninstall Cygwin/X (only)

[Dave Korn]

On 11/04/2010 04:21, Paul Bibbings wrote:

>   For
> instance, if I click on the view button and select `Not installed',
> suppose I select a package that I don't have - for example (I'm trying
> this now), aspell-dev 0.60.5-1.  Then, suppose I merely cycle through
> the Views and come back to `Not installed'. aspell-dev is no longer in
> the list, despite the fact that I have not done anything other than
> change the view.  It is no more installed now than it was before. 

  Well, the way I think of it is that when setup starts up, those displays
show you the current state of your installation; and what you do is change
things until they show you how you want it to be after setup completes, and
then when you've got everything how you want it to be, you hit "Next" to apply
your changes.

  BTW, in response to all the comments so far:

  I'm going to add right-click context menus because that's a small
incremental improvement that can be done now.  At least it'll bring an end to
the current craziness where trying to uninstall a whole bunch of
interdependent packages in one go is like one of those logical puzzle games
where every time you press a button a different subset of the lights toggle on
or off!

  All the other things: replacing the spinners by drop-downs, making the
chooser keyboard-navigable, tab-stopped and screen-reader friendly, require a
more-or-less complete rewrite of the PickView class.  It's a bigger job, and
not one that I'm going to get to until after gcc-4.5.0 is out.

cheers,
  DaveK


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

Usage of _exit(0) closes fd's of parent process

[tmhikaru]

Hi. I'm having an unusual problem in a program I'm trying to get
working in cygwin. My program fork()'s a child process to do a hostname
lookup, establishes a tcp connection in the parent, then has the child
_exit(0) itself. For some reason I don't understand, _exit is not just
closing the fd's of the child, but of the parent as well. From my
understanding, _exit is supposed to close the fd's of the process it is run
from only.

The program works correctly (That is to say, stays connected) if I
comment out the _exit and instead have it while (1) { sleep (1); }.
Obviously I would like to be able to kill off the child at some point, but
for testing this proved to me that either my expectation of how _exit is
supposed to work in cygwin is flawed, or _exit is.

Please let me know if I'm using this function call incorrectly, and
what behavior I should be expecting. If my expectation of how _exit is
supposed to act is correct, let me know and I'll file a bug report.


I am not subscribed to the cygwin mailing list, so please make sure
replies are sent to my email address as well as the list.

Thank you,
Hikaru

pgpaRJk7OXacU.pgp
Description: PGP signature

[ANNOUNCEMENT] Re: Updated: binutils-2.20.51-2

[Christopher Faylor]

A correction: The new version of binutils is binutils-2.20.51-2, not
binutils-2.19-51-2.  The -2 part is correct.  It reflects a botched -1
upload.

setup.exe will install the right version.  The typo was only in the
announcement.

cgf

--
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: How to uninstall Cygwin/X (only)

[Christopher Faylor]

On Sun, Apr 11, 2010 at 05:09:55AM +0100, Dave Korn wrote:
>On 11/04/2010 04:21, Paul Bibbings wrote:
>
>>   For
>> instance, if I click on the view button and select `Not installed',
>> suppose I select a package that I don't have - for example (I'm trying
>> this now), aspell-dev 0.60.5-1.  Then, suppose I merely cycle through
>> the Views and come back to `Not installed'. aspell-dev is no longer in
>> the list, despite the fact that I have not done anything other than
>> change the view.  It is no more installed now than it was before. 
>
>  Well, the way I think of it is that when setup starts up, those displays
>show you the current state of your installation; and what you do is change
>things until they show you how you want it to be after setup completes, and
>then when you've got everything how you want it to be, you hit "Next" to apply
>your changes.
>
>  BTW, in response to all the comments so far:
>
>  I'm going to add right-click context menus because that's a small
>incremental improvement that can be done now.  At least it'll bring an end to
>the current craziness where trying to uninstall a whole bunch of
>interdependent packages in one go is like one of those logical puzzle games
>where every time you press a button a different subset of the lights toggle on
>or off!

But the thing is, I'm not sure that just adding a drop-down is a useful
thing to do.  Maybe if you replaced the spinners with something
non-clickable that would be different.  But, having to tell everyone to
right-click doesn't seem like a huge improvement.  People still see the
spinner there, don't know what it is, and don't right or left click on
it.

cgf

--
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: Usage of _exit(0) closes fd's of parent process

[Christopher Faylor]

On Sun, Apr 11, 2010 at 01:48:51AM -0400, tmhik...@gmail.com wrote:
>Hi.  I'm having an unusual problem in a program I'm trying to get
>working in cygwin.  My program fork()'s a child process to do a
>hostname lookup, establishes a tcp connection in the parent, then has
>the child _exit(0) itself.  For some reason I don't understand, _exit
>is not just closing the fd's of the child, but of the parent as well.
>From my understanding, _exit is supposed to close the fd's of the
>process it is run from only.
>
>The program works correctly (That is to say, stays connected) if I
>comment out the _exit and instead have it while (1) { sleep (1); }.
>Obviously I would like to be able to kill off the child at some point,
>but for testing this proved to me that either my expectation of how
>_exit is supposed to work in cygwin is flawed, or _exit is.
>
>Please let me know if I'm using this function call incorrectly, and
>what behavior I should be expecting.  If my expectation of how _exit is
>supposed to act is correct, let me know and I'll file a bug report.

While it is theoretically possible to close handles in the parent process
it would be very unsual for Cygwin, or any program, to do something like
that.  And, in fact, Cygwin doesn't try to close handles in the parent
when it exits.

You need to go back and read http://cygwin.com/problems.html and then,
take a step back, and report the problem that you're seeing rather than
your conclusions about the problem.  For instance, what does "stays
connected" mean?  Are you using sockets, pipes, a file, shared memory,
etc.?

cgf

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