I occasionally see something similar. I can only describe it has managing to
log in and get ssh-add started by my first shell before windows has
sucessfully started something related to the network stack. In this case, ssh
(and maybe any other cygwin socket programs) simply wont work. I have to
On Fri, Jan 23, 2009 at 05:10:34AM -0500, Corinna Vinschen wrote:
> On Jan 22 18:05, avade...@certicom.com wrote:
> > On Thu, Jan 22, 2009 at 05:04:23PM -0500, Christopher Faylor wrote:
> > > On Thu, Jan 22, 2009 at 09:58:08PM +, Andy Koppe wrote:
> > > > avade...@certicom.com wrote:
> > > >>
On Thu, Jan 22, 2009 at 05:04:23PM -0500, Christopher Faylor wrote:
> On Thu, Jan 22, 2009 at 09:58:08PM +, Andy Koppe wrote:
> > avade...@certicom.com wrote:
> >>My WIN32 app is compiled under vc7 and uses signal() to trap SIGINT,
> >>SIGABRT and SIGTERM. If I run the application under consol
I ran across something under minTTY that I've confirmed behaves the same way
in rxvt, but differs under both the native terminal and console2. I expect
there is a good reason why this happens, and I'm quite willing to modify the
WIN32 app rather than pine for a change in minTTY to accomodate me.
I see this with an ARM cross compiler that had to be set to run with admin
privileges (or else Vista would prevent it from running). All my generated
objects were owned by me, but has zero for the permission mask.
So it could be that, or perhaps more likely, that you installed cygwin under a
diff
5 matches
Mail list logo