Skip to content
This repository has been archived by the owner on Feb 15, 2023. It is now read-only.

SIGTERM has no effect #243

Open
probablykasper opened this issue May 4, 2021 · 3 comments
Open

SIGTERM has no effect #243

probablykasper opened this issue May 4, 2021 · 3 comments

Comments

@probablykasper
Copy link

SIGTERM has no effect for npm run dev.

I'm using Svelte with Tauri (related issue: tauri-apps/tauri#1626), and this is causing leftover processes running after Tauri exits.

Reproduction

  1. Get the PID of the current terminal instance: echo $$
  2. npm run dev
  3. In a new terminal instance, run pkill -TERM -P <PID>

Info

macOS 10.15.7
Node.js v14.16.0
npm 6.14.11

@dRAT3
Copy link

dRAT3 commented Nov 8, 2021

Please fix this, it's annoying as hell, I have a bunch of node instances running for my language servers so I can't use killall, I have to use recursive shell functions just to terminate node

@orhun
Copy link

orhun commented Feb 3, 2022

I'm having the same problem here. Any updates on this?

@probablykasper
Copy link
Author

What @amrbashir said in tauri-apps/tauri#2883 might help:

A bit of an update, in svelte official template, I found out that they are using ignore instead of inherit

stdio: ['ignore', 'inherit', 'inherit'],

Switching it to inherit doesn't fix the whole issue but at least Ctrl+C terminates it properly.

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

No branches or pull requests

3 participants