Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add in timeout option to default socat "/opt/start.sh" #9

Open
dbrumley opened this issue Dec 4, 2024 · 0 comments
Open

Add in timeout option to default socat "/opt/start.sh" #9

dbrumley opened this issue Dec 4, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@dbrumley
Copy link

dbrumley commented Dec 4, 2024

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.

@dbrumley dbrumley added the bug Something isn't working label Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant