Greetings, Brian Inglis!
>> We are aware that there are many tutorials and Q on the net which deal with
>> exactly this subject. However, none of the proposed solutions worked for us.
The one Q should have get you started: since Cygwin 3.1 (IIRC, may be
earlier), the core was changed to use
Greetings, Christoph Lüders!
> I run cygwin 32-bit on Windows 10 Pro Build 19042. Cygwin is 3.2.0-1,
> openssh is 8.5p1-1.
> I use sshd to access the machine from afar. I notice (often multiple)
> processes of sshd.exe with 100% CPU load.
On Tue, Apr 27, 2021 at 3:14 PM Takashi Yano
wrote:
> On Tue, 27 Apr 2021 09:58:01 -0400
> "William M. \(Mike\) Miller via Cygwin" wrote:
> > I refreshed my Cygwin installation over the weekend, and ever since I
> have
> > not been able to run gdb under emacs as I previously had done. I use M-x
On 2021-04-27 04:37, Peter Pfannenschmid wrote:
However, today we have run into an issue with cron. Please see the attached logs
for details.
Additional notes:
- O/S is Windows Server 2019 Standard x64
- The cyg_server user has been created by cron-config, and we didn't change
anything in
Linux 5.12 Frozen Wasteland added features and changes:
add AMD 0x800a EDX:20 v_spec_ctrl virtual speculation control support
add Intel 0x0007 ECX:24 bus_lock_detect bus lock detect debug exception
---
winsup/cygwin/fhandler_proc.cc | 2 ++
1 file changed, 2 insertions(+)
diff --git
On Tue, 27 Apr 2021 09:58:01 -0400
"William M. \(Mike\) Miller via Cygwin" wrote:
> I refreshed my Cygwin installation over the weekend, and ever since I have
> not been able to run gdb under emacs as I previously had done. I use M-x
> gdb to start the gud interface, and as soon as I enter the
On 27/04/2021 18:00, Ken Brown wrote:
On 4/27/2021 12:52 PM, Ken Brown wrote:
On 4/27/2021 11:50 AM, Jon Turney wrote:
On 20/04/2021 21:13, Jon Turney wrote:
For ease of reviewing, this patch doesn't contain changes to generated
files which would be made by running ./autogen.sh.
I pushed
On 4/27/2021 12:52 PM, Ken Brown wrote:
On 4/27/2021 11:50 AM, Jon Turney wrote:
On 20/04/2021 21:13, Jon Turney wrote:
For ease of reviewing, this patch doesn't contain changes to generated
files which would be made by running ./autogen.sh.
I pushed this patch.
If you have an existing
On 4/27/2021 11:50 AM, Jon Turney wrote:
On 20/04/2021 21:13, Jon Turney wrote:
For ease of reviewing, this patch doesn't contain changes to generated
files which would be made by running ./autogen.sh.
I pushed this patch.
If you have an existing build directory, while you might get away
On 26/04/2021 16:03, Corinna Vinschen wrote:
On Apr 22 13:57, Corinna Vinschen wrote:
On Apr 21 18:40, Corinna Vinschen wrote:
On Apr 20 21:15, Jon Turney wrote:
On 20/04/2021 21:13, Jon Turney wrote:
* some object files are in a unexpected places in the build file hierarchy
(compared to
On 20/04/2021 21:13, Jon Turney wrote:
For ease of reviewing, this patch doesn't contain changes to generated
files which would be made by running ./autogen.sh.
I pushed this patch.
If you have an existing build directory, while you might get away with
invoking 'make' at the top-level, I
On 4/15/2021 11:01 AM, Ken Brown via Cygwin wrote:
On 4/15/2021 9:15 AM, sten.kristian.ivars...@gmail.com wrote:
[snip]
I tried SOCK_STREAM (and SOCK_SEQPACKET I think) for CYGWIN 3.2.0 but
that didn't work at all
As far as I understand, both all types on pretty much all
implementations
On 4/27/2021 9:19 AM, Corinna Vinschen wrote:
On Apr 26 15:37, Ken Brown wrote:
Following POSIX and Linux, allow a connected DGRAM socket's connection
to be reset (so that the socket becomes unconnected). This is done by
calling connect and specifing an address whose family is AF_UNSPEC.
---
On Apr 26 15:37, Ken Brown wrote:
> Following POSIX and Linux, allow a connected DGRAM socket's connection
> to be reset (so that the socket becomes unconnected). This is done by
> calling connect and specifing an address whose family is AF_UNSPEC.
> ---
> winsup/cygwin/fhandler_socket_inet.cc
Dear ladies and gentlemen,
thank you very much for providing the Cygwin DLL and ecosystem. We are using it
since many years without any problem.
However, today we have run into an issue with cron. Please see the attached
logs for details.
Additional notes:
- O/S is Windows Server 2019
15 matches
Mail list logo
