TIPC: Cluster Communication Protocol

Tracker: Bugs

5 Connect() should be supported for non-blocking sockets - ID: 2115069

Last Update: Settings changed ( ajstephens )

Details:

When using non-blocking TIPC sockets, a call to connect() will return
EWOULDBLOCK unconditionally.

TIPC should support non-blocking connect or at least return EOPNOTSUPP.

I'm using Linux 2.6.26 vanilla TIPC module.

Submitted:

Leandro Lucarella ( llucax ) - 2008-09-16 23:11

Priority:

Status:

Open

Resolution:

None

Assigned:

Nobody/Anonymous

Category:

Missing

Group:

None

Visibility:

Public

Comment ( 1 )

Date: 2008-10-01 20:54 Sender: ajstephens TIPC 1.7.6 contains a fix so that a request for a non-blocking connect returns EOPNOTSUPP. (Added in the -rc3 release.) This item has now been categorized as "missing", since support for the non-blocking form of connect() is a legitimate request; however, it remains unassigned at this point in time.

Log in to comment.

Attached File

Changes ( 2 )

Field	Old Value	Date	By
category_id	Interface	2008-10-28 17:31	ajstephens
category_id	None	2008-10-01 20:54	ajstephens

TIPC: Cluster Communication Protocol

Tracker: Bugs

Comment ( 1 )

Log in to comment.

Attached File

No Files Currently Attached

Changes ( 2 )

About SourceForge

Find Software

Develop Software

Community

Help