Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Handle sendto() function failure conditions #333

Merged
merged 1 commit into from
Jan 20, 2017
Merged

Handle sendto() function failure conditions #333

merged 1 commit into from
Jan 20, 2017

Commits on Jan 20, 2017

  1. Handle sendto() function failure conditions 

    The sendto() function can fail because of  multiple conditions.
Currently we are handling few conditions. If there is an error due
to another condition, the process gets stuck in repeatedly trying
to call sendto() function and failing with the same error condition.
For example, when awa session is established and after that
network interface goes down(ex. ethernet cable is removed),
the sendto() fuction fails with error 'ENETUNREACH'. This error
is not handled and the process gets stuck in repeatedly calling
sendto() fuction. There are also other possible error conditions.
In this change handling all error conditions, so that process
does not get stuck in endless loop.

Ref: AWA-311
Signed-off-by: Pranit Tanaji Sirsat <[email protected]>
    @pranit-sirsat-imgtec
    pranit-sirsat-imgtec committed Jan 20, 2017
    Configuration menu
    Copy the full SHA
    312cc24 View commit details
    Browse the repository at this point in the history