mafintosh / mafintosh/why-is-node-running

In Windows 10 the CLI version returns unknown PID

Open
#50 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
JavaScript
Stars
1.9k
Forks
52
PR merge metrics
No merged PRs in 30d

Description

After running from CLI and getting this PID:

kill -SIGUSR1 11020 for logging

We can't find that PID in the active process:

$ ps
      PID    PPID    PGID     WINPID   TTY         UID    STIME COMMAND
    14264   13280   13280      15272  cons0    1049692 18:36:57 /c/Program Files/nodejs/node
    13280   11132   13280      15860  cons0    1049692 18:36:57 /usr/bin/sh
    11132       1   11132      11132  cons0    1049692 17:34:12 /usr/bin/bash

$ bash: kill: (11020) - No such process

Trying with the active PIDs we get some messages but not the log:

$ kill -SIGUSR1 14264
      1 [sig] sh 14264! sigpacket::process: Suppressing signal 30 to win32 process (pid 15272)

$ kill -SIGUSR1 13280
      User defined signal 1

Any idea?

Thanks

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the CLI behavior on Windows 10 and compare the PID it reports with the active processes shown by ps. Check how SIGUSR1 is delivered to the Node process; done means the reported PID identifies the intended process and produces the expected logging output.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.