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

How to configure the timeout for idle shutdown? #91

Closed
andrewhavens opened this Issue Nov 15, 2016 · 5 comments

Comments

Projects
None yet
4 participants
@andrewhavens

andrewhavens commented Nov 15, 2016

I find that the default idle shutdown timeout is too aggressive for me. I'd like to adjust it to be at least an hour or more. Is it currently possible to configure this timeout? If not, can you please point me in the right direction so that I can try to submit a pull request?

@evanphx

This comment has been minimized.

Show comment
Hide comment
@evanphx

evanphx Jan 7, 2017

Member

You can add the -timeout flag to puma-dev to control how long it will wait.

Member

evanphx commented Jan 7, 2017

You can add the -timeout flag to puma-dev to control how long it will wait.

@evanphx evanphx closed this Jan 7, 2017

@concept47

This comment has been minimized.

Show comment
Hide comment
@concept47

concept47 Mar 31, 2017

@evanphx is there a way to put this in a configuration variable, or does it have to to be run from the command line all the time?

concept47 commented Mar 31, 2017

@evanphx is there a way to put this in a configuration variable, or does it have to to be run from the command line all the time?

@harigopal

This comment has been minimized.

Show comment
Hide comment
@harigopal

harigopal Apr 12, 2017

@concept47 You can pass options along with the -install flag to set those for the background service.

$ puma-dev -install -timeout 180m
$ ps -e | grep puma-dev
/usr/local/Cellar/puma-dev/0.10/bin/puma-dev -launchd -dir ~/.puma-dev -d dev -timeout 3h0m0s

harigopal commented Apr 12, 2017

@concept47 You can pass options along with the -install flag to set those for the background service.

$ puma-dev -install -timeout 180m
$ ps -e | grep puma-dev
/usr/local/Cellar/puma-dev/0.10/bin/puma-dev -launchd -dir ~/.puma-dev -d dev -timeout 3h0m0s
@concept47

This comment has been minimized.

Show comment
Hide comment
@concept47

concept47 Apr 12, 2017

that just screwed things up for some reason. Now all I see in my logs is
Error listening: accept tcp 0.0.0.0:0: accept: invalid argument

concept47 commented Apr 12, 2017

that just screwed things up for some reason. Now all I see in my logs is
Error listening: accept tcp 0.0.0.0:0: accept: invalid argument

@concept47

This comment has been minimized.

Show comment
Hide comment
@concept47

concept47 Apr 12, 2017

Figured out the problem, I have Apache running on port 80 and had to run puma-dev on port 81. Thanks @harigopal

concept47 commented Apr 12, 2017

Figured out the problem, I have Apache running on port 80 and had to run puma-dev on port 81. Thanks @harigopal

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment