From: cygwin-help@cygwin.com
To: listarch-cygwin@sourceware.org
Subject: ezmlm warning
Date: Thu, 30 Sep 2004 11:01:00 -0000 [thread overview]
Message-ID: <1096529271.11019.ezmlm-warn@cygwin.com> (raw)
Hi! This is the ezmlm program. I'm managing the
cygwin@cygwin.com mailing list.
Messages to you from the cygwin mailing list seem to
have been bouncing. I've attached a copy of the first bounce
message I received.
If this message bounces too, I will send you a probe. If the probe bounces,
I will remove your address from the cygwin mailing list,
without further notice.
I've kept a list of which messages from the cygwin mailing list have
bounced from your address.
Copies of these messages may be in the archive.
To retrieve a set of messages 123-145 (a maximum of 100 per request),
send an empty message to:
<cygwin-get.123_145@cygwin.com>
To receive a subject and author list for the last 100 or so messages,
send an empty message to:
<cygwin-index@cygwin.com>
Here are the message numbers:
96961
--- Enclosed is a copy of the bounce message I received.
Return-Path: <u.jakobus@emss.de>
Received: (qmail 962 invoked from network); 18 Sep 2004 14:01:17 -0000
Received: from unknown (HELO mail.emss.co.za) (196.44.35.53)
by sourceware.org with SMTP; 18 Sep 2004 14:01:17 -0000
Received: from [172.16.1.30] (uj-ntbk.emss.co.za [172.16.1.30])
by mail.emss.co.za (8.13.1/8.13.1) with ESMTP id i8IE1Cgl024647
for <cygwin-return-96961-listarch-cygwin=sourceware.org@cygwin.com>; Sat, 18 Sep 2004 16:01:12 +0200 (SAST)
(envelope-from u.jakobus@emss.de)
Message-ID: <414C3FA3.5040901@emss.de>
Date: Sat, 18 Sep 2004 16:01:07 +0200
From: Ulrich Jakobus <u.jakobus@emss.de>
Organization: EM Software & Systems GmbH
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803
X-Accept-Language: de, en, en-us
MIME-Version: 1.0
To: cygwin-return-96961-listarch-cygwin=sourceware.org@cygwin.com
Subject: Re: Cvsnt doesn't work anymore after cygwin upgrade to 1.5.11
References: <414C3E81.1000803@emss.de>
In-Reply-To: <414C3E81.1000803@emss.de>
X-Enigmail-Version: 0.85.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-MailScanner-Information: Please contact the ISP for more information
X-MailScanner: Found to be clean
X-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (score=-4.808,
required 5, AWL 0.09, BAYES_00 -4.90)
Hello,
>
> I just upgraded to cygwin 1.5.11, great that there is a new release. But, I
> use wincvs to get my cvs code, after the upgrade that doesn't work anymore,
> cvs just hangs. Doing just "cvs -z9 update" hangs forever, after
> downgrading
> to 1.5.10, it works again, anyone having an idea?
>
no idea, but problem with cygwin 1.5.11 confirmed using cvsnt 2.0.41 with
ssh from OpenSSH / cygwin. This "hangs forever" in cygwin is here:
.... (cut) ...
198 15830240 [main] ssh 412 readv: readv (3, 0x22CD30, 1) nonblocking, sigcatc
hers 3
112 15830352 [main] ssh 412 peek_socket: considering handle 0x6D0
81 15830433 [main] ssh 412 peek_socket: adding read fd_set , fd 3
106 15830539 [main] ssh 412 peek_socket: WINSOCK_SELECT returned 1
95 15830634 [main] ssh 412 fhandler_base::ready_for_read: read_ready 1, avail
1
131 15830765 [main] ssh 412 readv: 592 = readv (3, 0x22CD30, 1), errno 0
428 15831193 [main] ssh 412 cygwin_select: 7, 0x100EFB40, 0x100EFB50, 0x0, 0x0
145 15831338 [main] ssh 412 dtable::select_read: fd 3
121 15831459 [main] ssh 412 dtable::select_read: fd 4
116 15831575 [main] ssh 412 dtable::select_write: fd 5
88 15831663 [main] ssh 412 cygwin_select: to NULL, ms FFFFFFFF
80 15831743 [main] ssh 412 cygwin_select: sel.always_ready 0
263 15832006 [main] ssh 412 start_thread_socket: Handle 0x6D0
87 15832093 [main] ssh 412 start_thread_socket: Added to readfds
1360 15833453 [main] ssh 412 start_thread_socket: exitsock 0x648
219 15833672 [main] ssh 412 start_thread_socket: stuff_start 0x22EC54
133 15833805 [select_socket] ssh 412 thread_socket: stuff_start 0x100FC734
142 15833947 [main] ssh 412 select_stuff::wait: m 3, ms 4294967295
May be that helps in tracing down the problem? When just using "cygwin1.dll"
as of 1.5.10 then it works again.
Ulrich
next reply other threads:[~2004-09-30 7:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-30 11:01 cygwin-help [this message]
[not found] <1557166949.6367.ezmlm-warn@cygwin.com>
2019-05-06 19:04 ` Chris Wagner
2019-05-06 19:26 ` Brian Inglis
-- strict thread matches above, loose matches on Subject: below --
2017-08-14 9:22 cygwin-help
2016-11-02 10:43 Andrey ``Bass'' Shcheglov
2016-11-02 13:05 ` Eric Blake
2016-11-02 13:13 ` cyg Simple
2016-11-02 14:52 ` Herbert Stocker
2016-11-02 14:55 ` Jack
2016-11-02 13:05 ` cyg Simple
2015-10-05 9:09 cygwin-help
2010-02-07 14:38 cygwin-help
2009-09-14 10:29 cygwin-help
2005-06-15 16:28 cygwin-help
2004-06-08 16:19 cygwin-help
2001-12-20 23:02 cygwin-help
[not found] <955193687.11707.ezmlm-warn@sourceware.cygnus.com>
2000-04-10 1:08 ` Don Sharp
2000-04-10 10:15 ` Chris Faylor
[not found] ` <006301bfa32a$cbeeec10$5f0f4dd1@TIMYX18EWDT6RQ>
2000-04-10 13:36 ` Chris Faylor
2000-04-10 13:44 ` Jeff Sturm
2001-04-16 6:30 ` Chris Faylor
2001-09-04 23:46 ` Chris Faylor
2001-09-05 4:06 ` Don Sharp
[not found] ` <38F1E5D0.262ED39B@sigma6.com>
2000-04-11 1:07 ` Don Sharp
[not found] ` <200004101712.NAA09157@rtl.cygnus.com>
2000-04-11 1:17 ` Don Sharp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1096529271.11019.ezmlm-warn@cygwin.com \
--to=cygwin-help@cygwin.com \
--cc=listarch-cygwin@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).