From: Jay Foster <jay.foster@systech.com>
To: 'Matt Jerdonek' <maj1224@yahoo.com>, Andrew Lunn <andrew@lunn.ch>
Cc: Discussion eCos <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] TCP close(...) action
Date: Wed, 22 Oct 2003 16:17:00 -0000 [thread overview]
Message-ID: <80B97DE95AEED311BA580050047FE98494F751@mail.systech.com> (raw)
You could try sending the process a signal with kill(). SIGUSR1 might work.
-----Original Message-----
From: Matt Jerdonek [mailto:maj1224@yahoo.com]
Sent: Wednesday, October 22, 2003 9:06 AM
To: Andrew Lunn
Cc: Discussion eCos
Subject: Re: [ECOS] TCP close(...) action
> If you re-write your test program to use POSIX
> threads, it should then be possible to run it on
> linux, SunOS, *BSD etc. We can then decide if this
> is right or wrong.
>
> Andrew
>
> --
I ran the program on linux and got the same result
(the close did not wake the recv). So, I guess that
eCos is behaving correctly.
As I mentioned before, I have a workaround using
cyg_thread_release(..). Does anyone know of a POSIX
method for waking the recv other than ending and
restarting the thread?
Thanks,
-- Matt
__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next reply other threads:[~2003-10-22 16:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 16:17 Jay Foster [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-18 18:24 Matt Jerdonek
2003-10-18 18:30 ` Gary Thomas
2003-10-20 15:25 ` Matt Jerdonek
2003-10-21 17:38 ` Christoph Csebits
2003-10-21 18:35 ` Andrew Lunn
2003-10-22 16:06 ` Matt Jerdonek
2003-10-22 17:14 ` Nick Garnett
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=80B97DE95AEED311BA580050047FE98494F751@mail.systech.com \
--to=jay.foster@systech.com \
--cc=andrew@lunn.ch \
--cc=ecos-discuss@sources.redhat.com \
--cc=maj1224@yahoo.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).