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.

Sign up for GitHub

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

Jump to bottom

Add option for kill signal #48

Open
fivethreeo opened this issue Feb 10, 2021 · 1 comment
Open

Add option for kill signal #48

fivethreeo opened this issue Feb 10, 2021 · 1 comment

Comments

@fivethreeo
Copy link

I need to send SIGINT and not SIGKILL, SIGTERM would be good too. On windows I am not sure if there is antyhing like this.
@kachkaev
Copy link

kachkaev commented Jul 26, 2022 •
edited
Loading

I used yarn kill-port 3000 in CI but then realised it was not finishing the process the way I was expecting. A file that was supposed to be written on SIGINT was not there, so I switched to kill -2 $(lsof -t -i:3000) for now. This is Linux-only, but does the job in my case.

Having kill-port SIGINT 3000 would be great! List of signals: https://unix.stackexchange.com/a/317496

@kachkaev kachkaev mentioned this issue Jul 26, 2022
Merged
@repkam09 repkam09 mentioned this issue Jun 6, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fivethreeo @kachkaev