Skip to main content
Unix & Linux

Return to Answer

replaced http://serverfault.com/ with https://serverfault.com/
Source Link
Community Bot
Community Bot
  • 1

Hit this before in my life... the TIME_WAIT is an artifact of TCP/IP so you are stuck with it. It can be tweaked via /proc (see serverfault 23385serverfault 23385) but a better way would be a solution that opened a persistent socket that works as long as needed.

  generate_lots_of_lines | ssh myhost 'while read line; do echo ":$line"; done;'

This way you can have one connection do many things based on what the client sends the server.

Hit this before in my life... the TIME_WAIT is an artifact of TCP/IP so you are stuck with it. It can be tweaked via /proc (see serverfault 23385) but a better way would be a solution that opened a persistent socket that works as long as needed.

  generate_lots_of_lines | ssh myhost 'while read line; do echo ":$line"; done;'

This way you can have one connection do many things based on what the client sends the server.

Hit this before in my life... the TIME_WAIT is an artifact of TCP/IP so you are stuck with it. It can be tweaked via /proc (see serverfault 23385) but a better way would be a solution that opened a persistent socket that works as long as needed.

  generate_lots_of_lines | ssh myhost 'while read line; do echo ":$line"; done;'

This way you can have one connection do many things based on what the client sends the server.

Bounty Awarded with 50 reputation awarded by nicoulaj
Source Link
Gilbert
Gilbert
  • 864
  • 6
  • 6

Hit this before in my life... the TIME_WAIT is an artifact of TCP/IP so you are stuck with it. It can be tweaked via /proc (see serverfault 23385) but a better way would be a solution that opened a persistent socket that works as long as needed.

  generate_lots_of_lines | ssh myhost 'while read line; do echo ":$line"; done;'

This way you can have one connection do many things based on what the client sends the server.