问题原文
原帖链接 · Pizza · CC BY-SA 4.0
I have a Windows server 2016 machine that needs to run an file that uses the cli, remotely using SSH.
It is known that logging out of an SSH connection terminates processes that were started by the ssh user. On linux machines, one may use solutions such as nohup or screen, resulting a process not being killed once logging off.
Such solutions won't work on windows machines though, and I'm looking for a way to prevent a process from getting terminated once logged out.
- My client is an Ubuntu machine
- My Windows server 2016 runs OpenSHH, with PowerShell as a default shell
- My program is set to work in daemon mode, and no cmd or powershell windows are left open
- Using
Get-Process -Name proc_nameshows the process is indeed running - Using
Get-Processafter SSH logout yields no such process
Things I also tried:
- Running the
.exefile usingcmd. - Running a
.batand.psfiles that starts the.exewith its arguments.
Is there a way to tackles this problem on a windows machine?
已采纳解答
原帖链接 · Pizza · CC BY-SA 4.0
After spending much time digging for solutions, I found the absolute correct way of doing so using PowerShell.
It seems like it is one of those cmdlets less used or documented online, and is almost impossible to figure out on your own using the MSDN documentation, unless you're already very familiar with the huge world of Wmi Objects.
In short:
Assuming I have a program foo.exe that needs to run on background with the arguments -a, -b and bar, I should be using the exact command:
Invoke-WmiMethod -Path 'Win32_Process' -Name Create -ArgumentList 'C:\Users\foo\Desktop\foo.exe -a -b bar'
Of course if your exe is a "known" exe (either by default, such as notepad or ping) or added by you, a full path is not needed when using the -ArgumentList and exe name would be sufficient (notepad, ping, and etc..).
Additional parameters:
Invoke-WmiMethod supports additional parameters such as -Credential, -ComputerName (a good way to use a local PS to Invoke something on a remote machine without using SSH) , -Impersonation and many more documented here.
Cmdlet syntax explanation and additional cmdlet tools:
- The
-Pathargument directs to aWmiObjectname. There are dozens ofWmiObjects, each with manyMethodsandProperties. - The
-Nameargument directs the usedMethod. - To list all available
Wmi-ObjectsuseGet-WmiObject -List(very difficult to locate your needed object this way). - To list and view all available
Win32_ProcessMethodsandPropertiesuse
Get-WmiObject -List |where{$_.name -match '^Win32_Process$'}
This will return an output of this structure:
NameSpace: ROOT\cimv2
Name Methods Properties
---- ------- ----------
Win32_Process {Create, Terminat... {Caption, CommandLine, CreationClassName, CreationDate...}
And of course using |Select-Object -ExpandProperty (_your_property_here_) will reveal all available Methods such as Create we used in the command above, and all available Properties (which we did not use).
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
