On Sat, Aug 25, 2012 at 11:35:06PM -0400, starlight.201...@binnacle.cx wrote:
>Hello,
>
>Just upgraded from 1.7.5 to 1.7.16.
>
>Curiously the NoMachine 'nxclient' application doesn't work when the
>latest 'cygwin1.dll' is copied into it's bin directory.
>
>However it works fine with the older 1.7.5
The logs say that
NXWin.exe
is failing on startup with an
exit code of 259
If anyone thinks then can make sense of
it, I could run 'procmon64' on NXWin and
trace the Windows systems calls in it.
Could run any applicable CYGWIN tools
as well.
--
Problem reports: http://cygwin.com/probl
Missed that section, was reading from my phone. Anyway, how about
instead of chastising someone for trying to help, you come up with an
alternative solution?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwi
Hello,
Just upgraded from 1.7.5 to 1.7.16.
Curiously the NoMachine 'nxclient' application
doesn't work when the latest 'cygwin1.dll'
is copied into it's bin directory.
However it works fine with the older 1.7.5
'cygwin1.dll'. Using the 1.7.5 DLL with
'nxclient' does not seem to cause problems
w
On 25/08/2012 11:45 AM, K Stahl wrote:
cat "$LOG" | gzip > "$LOG.old.gz" > "$LOG"
Don't have access to my machine at the moment, but try adding the '-c'
options to gzip (e.g. gzip -c ...)
He said he tried that and it didn't work...
Ryan
--
Problem reports: http://cygwin.com/problems.ht
So I was trying to debug why my new build of rxvt-unicode crashes as
soon as I try to do anything interesting, and found that gdb was
unusable. I was trying to type 'set args' but the space key would not work.
No, it's not my keyboard.
In the same terminal, I can type spaces all day long, but
> cat "$LOG" | gzip > "$LOG.old.gz" > "$LOG"
Don't have access to my machine at the moment, but try adding the '-c'
options to gzip (e.g. gzip -c ...)
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/d
Dear CYGWIN,
Upgraded to 1.7.16-1 from 1.7.14-1
Seemed to be ok. But after some while using noticed ssh processes died suddenly
- all attempts to start new ones fail.
Noticed sshd crashed and refused to start with errors:
Here is an extract of sshd.log (from the top):
c:\cygwin\tmp>type ..\va
Achim Gratz writes:
[...]
Hit send too soon... here's the patch set again without the typos.
>From 8a930eb8adc4d9364ea0d6c8f63be448c539b448 Mon Sep 17 00:00:00 2001
From: Achim Gratz
Date: Sat, 25 Aug 2012 08:19:12 +0200
Subject: [PATCH 1/3] Protect ORIGINAL_PATH and control behaviour by
CYGWIN_
9 matches
Mail list logo