-
-
Notifications
You must be signed in to change notification settings - Fork 196
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
Allow foreground execution for s6 style service #35
Comments
So you need a |
starting FTL with the command EDIT taken from https://github.com/pi-hole/FTL#command-line-arguments |
ah yup |
Although you have been able to achieve what you need using
|
Update Dependencies, and Update Rust to nightly-2018-06-20
In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:
How familiar are you with the codebase?:
6
Simple request: since backgrounding/daemonizing is the default of pihole-FTL, please provide a
-f
argument to run it in the foreground to provide some more versatility with other supervisor style service managers like s6.I just converted the pi-hole docker image to use s6-overlay, all my other services for the docker-pi-hole container have a option to run them int he foreground so that s6-supervisor can properly watch the long running process (also intake logs) and restart it if something goes wrong.
More details on s6 services: http://www.skarnet.org/software/s6/servicedir.html see the bullet points, the 5th in particular:
s6 will just restart a service over and over when the process goes into background mode (learned this with php-fpm) since it is a supervisor style service manager, the exit of the
run
script means the service stopped in s6's mind and it triggers another run unless it was just told to stop the service.I can work around this for now with something silly like
while pgrep pihole-FTL ; do sleep 5 ; done
at the end of my s6 service run script, so no rush.The text was updated successfully, but these errors were encountered: