From: "Enzo Michelangeli" <em@em.no-ip.com>
To: <cygwin@cygwin.com>
Cc: "\"Brian Ford\"" <ford@vss.fsi.com>
Subject: Re: 1.5.9-1: socket() appears NOT to be thread-safe
Date: Thu, 15 Apr 2004 04:04:00 -0000 [thread overview]
Message-ID: <013701c4229e$9cd68c60$0200a8c0@em.noip.com> (raw)
I wrote:
----- Original Message -----
From: "Enzo Michelangeli" <em@em.no-ip.com>
To: <cygwin@cygwin.com>
Cc: ""Brian Ford"" <ford@vss.fsi.com>
Sent: Thursday, April 15, 2004 11:16 AM
Subject: Re: 1.5.9-1: socket() appears NOT to be thread-safe
[...]
> By the way, even in case of no error the socket calls return the same
> value of fd. Is this OK??
Please ignore the two lines above: I forgot to remove them after fixing
the bug that had prompted me to write them in first place :-) The fd are
obviously different, as shown in the sample output.
Enzo
P.S. By the way, Corinna: couldn't I just put my gethostbyname_r() in the
public domain, rather than going through the bureaucratic chore of the
copyright assignment? Also because I feel that implementing it through
mutex-protection of gethostbyname(), as I did, is just a quick hack, as it
unnecessarily blocks other threads that could access the name server in
parallel (with separate network I/O and properly re-entrant code). It may
help other implementors to solve an urgent problem, but I don't think it
should be released as part of the Cygwin code.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2004-04-15 4:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 4:04 Enzo Michelangeli [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-14 10:43 Enzo Michelangeli
2004-04-14 13:22 ` Corinna Vinschen
2004-04-14 17:06 ` Brian Ford
2004-04-15 3:17 ` Enzo Michelangeli
2004-04-15 4:14 ` Christopher Faylor
2004-04-15 17:41 ` Christopher Faylor
2004-05-22 16:59 ` Brian Ford
2004-05-22 19:08 ` Christopher Faylor
2004-06-10 15:21 ` Brian Ford
2004-06-10 17:37 ` Brian Ford
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='013701c4229e$9cd68c60$0200a8c0@em.noip.com' \
--to=em@em.no-ip.com \
--cc=cygwin@cygwin.com \
--cc=ford@vss.fsi.com \
/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).