You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now we have no default timeout for socat, so if someone connects but never sends anything (or the problem is expecting a certain number of reads, but they don't happen), the process won't end. This can quickly use up PIDs for the container (default for me is 20).
Solution would be to add to the default "socat -T60" (60 seconds) or "socat -T600" (5 minutes, probably more reasonable) to the examples. This will help ensure contributors are pushing stable challenges.
The text was updated successfully, but these errors were encountered:
Right now we have no default timeout for socat, so if someone connects but never sends anything (or the problem is expecting a certain number of reads, but they don't happen), the process won't end. This can quickly use up PIDs for the container (default for me is 20).
Solution would be to add to the default "socat -T60" (60 seconds) or "socat -T600" (5 minutes, probably more reasonable) to the examples. This will help ensure contributors are pushing stable challenges.
The text was updated successfully, but these errors were encountered: