How can I start a background job in Powershell that outlives it's parent?

前端 未结 4 773
无人共我
无人共我 2020-12-09 16:17

Consider the following code:

start-job -scriptblock { sleep 10; cmd /c set > c:\\env.txt; }
exit

The background job is killed when the p

相关标签:
4条回答
  • 2020-12-09 16:50

    You will have to start a process:

    start-process powershell -ArgumentList "sleep 10; cmd /c set > c:\env.txt" -WindowStyle hidden
    
    0 讨论(0)
  • 2020-12-09 16:53

    If you use Start-Process, you create a new child process that has your powershell session as its parent process. If you kill the powershell parent process that starts this, the new process will be orphaned and keep running. It will, however, not survive if you kill the parent's process tree

    Start-Process -FilePath notepad.exe
    

    Powershell cannot start a new independent process outside of its process tree for you. However, this can be done in Windows using CreateProcess and this functionality is exposed through WMI. Luckily, you can call that from powershell:

    Invoke-WmiMethod -Class Win32_Process -Name Create -ArgumentList notepad.exe
    

    This way, the new process will also keep running if the process tree is killed, because the new process does not have your powershell session as a parent, but the WMI host process.

    0 讨论(0)
  • 2020-12-09 17:03

    If found that using Invoke-Command was able to bypass the restriction that the background job dies with it's parent. The nice thing is that the syntax is almost the same as with start-job, so the scriptblock can be kept as is.

    start-job -scriptblock { sleep 10; cmd /c set > c:\env.txt; }
    

    would just turn into

    Invoke-Command -ComputerName . -AsJob -scriptblock { sleep 10; cmd /c set > c:\env.txt; }
    

    and suddenly survive the death of it's parent (probably because invoke-command is fit to run programs on another computer so the parent can never matter to it)

    0 讨论(0)
  • 2020-12-09 17:13

    You can also do it like that

    $a = start-job -scriptblock { sleep 10; cmd /c set > c:\env.txt; }
    Register-ObjectEvent -InputObject $a -EventName StateChanged -SourceIdentifier "finished"
    $b = Wait-Event -SourceIdentifier "finished"
    exit
    

    Your script will wait for the end of the scriptblock to finish.

    0 讨论(0)
提交回复
热议问题