Java processes forked from Powershell will die when CTRL+C is used or when Powershell terminal window is closed.

Steps to reproduce

Open a powershell terminal in Linux. You can use any gnome-terminal or terminator, doesn’t seem to matter what Terminal program you are using.

Run a program that runs a Jetty service in the background. Example: Lucidworks Fusion 4.2.6

/home/ndipiazza/.fusion/4.2.6/bin/fusion start

Now close the terminal.

Notice the Java binaries that were opened will killed when the powershell terminal dies.

Repeating these same steps using a normal terminal will not have this problem. It is only when you start the program from a powershell terminal that this happens.

video capture here: https://www.youtube.com/watch?v=MniUDVmiJGo&feature=youtu.be

This also does not happen on Windows.

Expected behavior

Should keep running after terminal is closed.

Actual behavior

Forked java processes die along with powershell. Seem to also die intermittently when you use “CTRL+C”.

Environment data

Name                           Value
----                           -----
PSVersion                      7.0.2
PSEdition                      Core
GitCommitId                    7.0.2
OS                             Linux 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

[mklement0]

@vmiheer, I’ve posted an answer to your SO question, but the same information can be found in #12090.

Again, if there’s a desire to bring nohup functionality more directly to PowerShell, I suggest creating a new feature request.

[vmiheer]

This is related: https://stackoverflow.com/questions/64707869/what-is-the-equivalent-of-nohup-in-linux-powershell I was asking explicitly how to do Start-Job which is equivalent to nohup.

<div>Stack Overflow</div><div>What is the equivalent of 'nohup' in linux PowerShell?</div><div>I very well know existence of duplicate question. But that question is marked answered and I don't think it at all answers the original question. The $ nohup command keeps executing command even if...</div>