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

Processes don't always exit on Ctrl-C (SIGINT) #169

Open
sbleon opened this issue Mar 10, 2022 · 0 comments
Open

Processes don't always exit on Ctrl-C (SIGINT) #169

sbleon opened this issue Mar 10, 2022 · 0 comments

Comments

@sbleon
Copy link

sbleon commented Mar 10, 2022

Thanks for the great software!

For some reason, the processes don't always get signaled to exit when I press Ctrl-C.

When things work correctly, the output looks like this:

11:51:55 AM docker.1  |  mailhog-1   | [APIv1] KEEPALIVE /api/v1/events
11:52:55 AM docker.1  |  mailhog-1   | [APIv1] KEEPALIVE /api/v1/events
^C[WARN] Interrupted by User
[DONE] Killing all processes with signal  SIGINT
11:53:42 AM docker.1  |  Gracefully stopping... (press Ctrl+C again to force)
11:53:42 AM webpack.1 |  <i> [webpack-dev-server] Gracefully shutting down. To force exit, press ^C again. Please wait...
11:53:42 AM docker.1  |  Container mailhog-1  Stopping
11:53:42 AM docker.1  |  Container postgres-1  Stopping
11:53:42 AM docker.1  |  Container cf-1  Stopping
11:53:42 AM sass.1    Exited with exit code SIGINT
11:53:42 AM cfformat.1 |  Stopping...
11:53:42 AM webpack.1 Exited Successfully
11:53:42 AM docker.1  |  Container mailhog-1  Stopped
11:53:42 AM docker.1  |  Container postgres-1  Stopped
11:53:44 AM cfformat.1 Exited with exit code null
11:53:53 AM docker.1  |  Container cf-1  Stopped
11:53:53 AM docker.1  |  Container httpd-1  Stopping
11:53:54 AM docker.1  |  canceled
11:53:54 AM docker.1  Exited with exit code null

When things don't work correctly, I see something like this:

12:09:04 PM docker.1  |  cf-1        | [INFO ] runwar.server: ******************************************************************************
12:09:04 PM docker.1  |  cf-1        | [INFO ] runwar.server: Server is up - http-port:8080 stop-port:35709 PID:140 version 4.5.2
^C

and I'm right back to my prompt.

I have not been able to identify any pattern around this behavior, but I've seen it happen in multiple applications that use nf.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant