|
|
|
|
||||||
| comp.protocols.tcp-ip TCP and IP network protocols. |
![]() |
|
|
LinkBack | Outils de la discussion |
|
|
#1 |
|
Messages: n/a
Hébergeur: |
hi all,
is there a way to make a connect block? iow, what status has the server to be in to make a connect block? in the state bound the connect fails, in the state listen the connect succeeds, even without accept. system is solaris 9. thanks for any reply. |
|
|
|
#2 |
|
Messages: n/a
Hébergeur: |
"adirtymindisajoyforever" <getridofthespam@yahoo.com> writes:
> is there a way to make a connect block? iow, what status has the > server to be in to make a connect block? in the state bound the connect > fails, in the state listen the connect succeeds, even without accept. > system is solaris 9. connect() blocks by default. What I *think* you're asking about is a way to make the server side avoid sending SYN-ACK until accept() is called. No, there's no way to do that on Solaris (or most systems for that matter). The kernel manages the connection queue on listen sockets. -- James Carlson, KISS Network <james.d.carlson@sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 |
|
|
|
#3 |
|
Messages: n/a
Hébergeur: |
James Carlson schreef: > "adirtymindisajoyforever" <getridofthespam@yahoo.com> writes: > > is there a way to make a connect block? iow, what status has the > > server to be in to make a connect block? in the state bound the connect > > fails, in the state listen the connect succeeds, even without accept. > > system is solaris 9. > > connect() blocks by default. > > What I *think* you're asking about is a way to make the server side > avoid sending SYN-ACK until accept() is called. No, there's no way to > do that on Solaris (or most systems for that matter). The kernel > manages the connection queue on listen sockets. Thanks for replying James. You were *thinking* right. I expected with a server having a listen(fd,2) and not accepting, the third connect to block but it does not. Apparently I am confused aout the meaning of the second parameter of the listen() system call. > > -- > James Carlson, KISS Network <james.d.carlson@sun.com> > Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 > MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 |
|
|
|
#4 |
|
Messages: n/a
Hébergeur: |
"adirtymindisajoyforever" <getridofthespam@yahoo.com> writes:
> Thanks for replying James. You were *thinking* right. I expected with > a server having a listen(fd,2) and not accepting, the third connect to > block > but it does not. Apparently I am confused aout the meaning of the > second parameter > of the listen() system call. It's a limit on the number of completed connections waiting to be accepted by the application. -- James Carlson, KISS Network <james.d.carlson@sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 |
|
![]() |
| Outils de la discussion | |
|
|