Исходное сообщение
"TCP reset" Отправлено PavelR, 01-Июн-11 22:20
Не. Походу таки я  не прав.   Generally the difference between close() and shutdown() is: close()   closes the socket id for the process but the connection is still   opened if another process shares this socket id.  The connection stays   opened both for read and write, and sometimes this is very important.   shutdown() breaks the connection for all processes sharing the socket   id.  Those who try to read will detect EOF, and those who try to write   will reseive SIGPIPE, possibly delayed while the kernel socket buffer   will be filled.  Additionally, shutdown() has a second argument which   denotes how to close the connection: 0 means to disable further   reading, 1 to disable writing and 2 disables both. Читал тут: http://www.faqs.org/faqs/unix-faq/socket/

Ваше сообщение
Имя*:
EMail:	Для отправки новых сообщений в текущей нити на email укажите знак ! перед адресом, например, !user@host.ru (!! - не показывать email). Более тонкая настройка отправки ответов производится в профиле зарегистрированного участника форума.
Заголовок*:
Сообщение*:	> Не. > Походу таки я не прав. > Generally the difference between close() and shutdown() is: close() > closes the socket id for the process but the connection > is still > opened if another process shares this socket id. The > connection stays > opened both for read and write, and sometimes this is > very important. > shutdown() breaks the connection for all processes sharing the socket > id. Those who try to read will detect EOF, > and those who try to write > will reseive SIGPIPE, possibly delayed while the kernel socket buffer > will be filled. Additionally, shutdown() has a second argument > which > denotes how to close the connection: 0 means to disable > further > reading, 1 to disable writing and 2 disables both. > Читал тут: http://www.faqs.org/faqs/unix-faq/socket/
	Введите код, изображенный на картинке: