public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Wai-Kong Sung <waikong@commdevices.com>
To: Sergey Okhapkin <sos@buggy.prospect.com.ru>
Cc: "gnu-win32@cygnus.com" <gnu-win32@cygnus.com>
Subject: Re: socket programming in Win95, concurrent server
Date: Thu, 29 Jan 1998 06:51:00 -0000	[thread overview]
Message-ID: <34D09840.8EBB6D4A@commdevices.com> (raw)
In-Reply-To: <01BD2CC5.C4450900@sos>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 825 bytes --]

Thanks! I fingure out this from your web site later. Anyway, signals
don't work very well in Win95 too. Later I swith to use the Win32 thread
instead the old unix way fork/exec. It works. Kinda! It stops once a
while for no reason. It seems to me the Berkeley socket in GNU-Win32 is
not really thread-safe. So I switch to winsock. It works but just that
Unix like anymore.

waikong

Sergey Okhapkin wrote:

> Wai-Kong Sung wrote:
> > I would like to know whether passing a child process inherit the
> socket
> > handle from the parent in gnuwin32/Win95.Ç??
> >
>
> Socket() call on windows95 creates a non-inherittable socket! Download
> patched cygwin.dll from my web page - it handles this bug of Win95.
>
> --
> Sergey Okhapkin, http://www.lexa.ru/sos
> Moscow, Russia
> Looking for a job

　　

  reply	other threads:[~1998-01-29  6:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-01-29  6:51 Sergey Okhapkin
1998-01-29  6:51 ` Wai-Kong Sung [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-01-19 17:06 Wai-Kong Sung

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=34D09840.8EBB6D4A@commdevices.com \
    --to=waikong@commdevices.com \
    --cc=gnu-win32@cygnus.com \
    --cc=sos@buggy.prospect.com.ru \
    /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).