Launch background job

[pelhu]

Hi dear Gert.

I can not run a background task with "&" at the end of the command line. My symbol "&" is simply ignored. Could you help me please?

Cordially Khamzat

[YuryAlkevich]

I have the same problem with SshClient. Neither 'command &' nor 'nohup command &' doesn't keep alive launched command in background after end of execution of RunCommand method

[darkoperator]

That is because no shell is created with that API call so there is no state. You will need to use a ShellStream for that. It will create a shell and you can write and read from the stream and it maintains state

…

Sent from my iPhone

On Apr 9, 2018, at 8:57 AM, YuryAlkevich ***@***.***> wrote: I have the same problem with SshClient. Neither 'command &' nor 'nohup command &' doesn't keep alive launched command in background after end of execution of RunCommand method — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[YuryAlkevich]

Thank you @darkoperator. Everything works fine via ShellStream

[sdlmw]

Hello @YuryAlkevich

I have the same a problem with you, Could you tell me how to use ShellStream? Thank you!

[dustinkerstein]

Just wanted to see if it was possible to post a working example of a background command working. I am running into the same issue and no matter how I call my command (sh, nohup, &, etc.) it still blocks execution. Is there a simple example of ShellStream posted somewhere? Thanks!

[dustinkerstein]

I managed to get the below using ShellStream working:

var stream = clientStart.CreateShellStream("input", 0, 0, 0, 0, 1000000);
Thread.Sleep(100); // Ugly but needed to wait a little or else shell isn't ready
stream.WriteLine("nohup sh -c '( ( command &>/dev/null ) & )'");

[gavin1970]

I have shellstream working. Maybe you can steal some ideas from here.

https://github.com/gavin1970/Linux-Commander/blob/master/Linux-Commander/common/Ssh.cs

[WojciechNagorski]

SSH.NET version 2024.0.0 has changed a lot. I'm closing the ticket, but if the problem still persists, please feel free to reopen or open a new ticket.