forked from Imagelibrary/rtems
a4cb8f0d28
Alexey S. Fadeyev <alexey@vocord.com>. Discussion follows: "Alexey S. Fadeyev" wrote: > So if I run this application it tell me : > > connect_task: Connection established > > accept somthing > > But if I try to connect to invalid port (3001 for example) it also tell me > that connection > established but bind_task did't accept it. So how I can find out in > connect_task does my connection realy > exist ? What type of socket is here? Blocking or non-blocking? I try used > select but it did't help - it > always tell me from connect_task that connection is valid. > Yep -- there was a problem alright. The connect() routine wasn't returning an error indication when it should have. Note that this problem was not limited to the loopback driver -- a refused connection from any server would return `success'.
#
# $Id$
#
This is the top level of the RTEMS directory structure. The following
is a description of the files and directories in this directory:
Makefile.in
The top-level Make command file used to build the C implementation
of RTEMS. [RTEMS assumes the use of GNU make.]
README
This file.
REQUIRES
A list of the other tools which are assumed to be installed
before RTEMS is built.
SUPPORT
Information on third-party support for RTEMS.
build-tools
This directory contains the source for various utilities
needed to build RTEMS.
make
Make command files "included" from those in the source distribution.
[RTEMS assumes the use of GNU make.]
patches
This directory contains patches for this release of RTEMS.
src
This directory contains the source code for the C
implementation of RTEMS as well as the test suites, sample
applications, Board Support Packages, Device Drivers, and
support libraries.