This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: TCP close(...) action
- From: Jay Foster <jay dot foster at systech dot com>
- To: 'Matt Jerdonek' <maj1224 at yahoo dot com>, Andrew Lunn <andrew at lunn dot ch>
- Cc: Discussion eCos <ecos-discuss at sources dot redhat dot com>
- Date: Wed, 22 Oct 2003 09:02:00 -0700
- Subject: RE: [ECOS] TCP close(...) action
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