public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: NGUYEN Thanh SILICOMP <thanh2.nguyen@orange-ftgroup.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Application is blocked on the while loop 	withinbsd_connect()   function
Date: Fri, 04 Jan 2008 14:54:00 -0000	[thread overview]
Message-ID: <477E481C.6050005@mlbassoc.com> (raw)
In-Reply-To: <477E05BC.5080804@orange-ftgroup.com>

NGUYEN Thanh SILICOMP wrote:
> Hi,
> 
> Yes, for solving the issue, i had to make a non blocking socket for 
> ftpclient. Instead of using fcntl() with F_GETFL or F_SETFL that is not 
> supported at this moment in Ecos,  I used ioctl with FIONBIO. My 
> application seems working good now.

Perhaps you could send a patch with your changes and we could
wrap them into the public source, with some CDL, etc?

> Andrew Lunn a écrit :
>> On Wed, Jan 02, 2008 at 11:57:34AM +0100, NGUYEN Thanh SILICOMP wrote:
>>  
>>> Hi all,
>>>
>>> Firstly, happy new year & best wished to all.
>>>
>>> I'm working on an application connecting to FTP server using ecos 
>>> ftpclient package.  I constate that the application waits for ever on 
>>> a blocking semaphore of cyg_tsleep() function when there is no ftp 
>>> server available.
>>>
>>> In fact, for connecting to ftp server, ftpclient uses connect() that 
>>> calls itself bas_connect() in which the while loop is used for 
>>> waiting for the connection etablishment or an error occurring :
>>>
>>> while ((so->so_state & SS_ISCONNECTING) && so->so_error == 0) {
>>>        error = tsleep((caddr_t)&so->so_timeo, PSOCK | PCATCH,
>>>                       netcon, 0);
>>>
>>>        if (error)
>>>            break;
>>>
>>> }
>>>
>>> The paramter timo of tsleep set to 0 makes cyg_tsleep waiting for a 
>>> blocking semaphore at line 325 of the file synch.c 
>>> (net/tcpip/current/src/ecos/synch.c). And the wait time is usually 
>>> long and triggers the watchdog process in my application.
>>>
>>> I would like to know that there is any way to set up a timeout on 
>>> socket before calling connect() so that the application will be able 
>>> to get out this blocking situation ?
>>>
>>> Any idea or sugestion will be appreciated.
>>>     
>>
>> Take a look at
>> http://www.developerweb.net/forum/showthread.php?p=13486.  You will
>> need to modify the ftpclient code to implement this scheme for
>> connect.
>>
>>         Andrew
>>
>>   
> 


-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

      reply	other threads:[~2008-01-04 14:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-02 11:02 [ECOS] Application is blocked on the while loop within bsd_connect() function NGUYEN Thanh SILICOMP
2008-01-03 11:55 ` Andrew Lunn
2008-01-04 10:09   ` [ECOS] Application is blocked on the while loop withinbsd_connect() function NGUYEN Thanh SILICOMP
2008-01-04 14:54     ` Gary Thomas [this message]

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=477E481C.6050005@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=thanh2.nguyen@orange-ftgroup.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).