首先遵循以下步骤:

以用户A登录A，生成一对认证密钥。不要输入密码:

a@A:~> ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/home/a/.ssh/id_rsa): 
Created directory '/home/a/.ssh'.
Enter passphrase (empty for no passphrase): 
Enter same passphrase again: 
Your identification has been saved in /home/a/.ssh/id_rsa.
Your public key has been saved in /home/a/.ssh/id_rsa.pub.
The key fingerprint is:
3e:4f:05:79:3a:9f:96:7c:3b:ad:e9:58:37:bc:37:e4 a@A

现在使用ssh创建一个目录~/。(目录可能已经存在，这没有问题):

a@A:~> ssh b@B mkdir -p .ssh
b@B's password: 

最后将a的新公钥追加到b@B:。Ssh /authorized_keys最后一次输入b的密码:

a@A:~> cat .ssh/id_rsa.pub | ssh b@B 'cat >> .ssh/authorized_keys'
b@B's password: 

从现在开始，你可以以B的身份从A以A的身份登录到B，无需密码:

a@A:~> ssh b@B

这样就可以不用输入密码了

ssh b@B "cd /some/目录;program-to-execute &”

我认为你必须把这些答案结合起来才能得到你想要的。如果将nohup与分号结合使用，并将整个内容用引号括起来，那么您将得到:

ssh user@target "cd /some/directory; nohup myprogram > foo.out 2> foo.err < /dev/null"

这似乎对我有用。使用nohup，您不需要将&附加到要运行的命令。此外，如果您不需要读取命令的任何输出，则可以使用

ssh user@target "cd /some/directory; nohup myprogram > /dev/null 2>&1"

将所有输出重定向到/dev/null

实际上，每当我需要在远程机器上运行复杂的命令时，我喜欢将命令放在目标机器上的脚本中，然后使用ssh运行该脚本。

例如:

# simple_script.sh (located on remote server)

#!/bin/bash

cat /var/log/messages | grep <some value> | awk -F " " '{print $8}'

然后我在源机器上运行这个命令:

ssh user@ip "/path/to/simple_script.sh"

If you run remote command without allocating tty, redirect stdout/stderr works, nohup is not necessary. ssh user@host 'background command &>/dev/null &' If you use -t to allocate tty to run interactive command along with background command, and background command is the last command, like this: ssh -t user@host 'bash -c "interactive command; nohup backgroud command &>/dev/null &"' It's possible that background command doesn't actually start. There's race here: bash exits after nohup starts. As a session leader, bash exit results in HUP signal sent to nohup process. nohup ignores HUP signal. If 1 completes before 2, the nohup process will exit and won't start the background command at all. We need to wait nohup start the background command. A simple workaroung is to just add a sleep: ssh -t user@host 'bash -c "interactive command; nohup backgroud command &>/dev/null & sleep 1"'

这个问题在几年前就被提出和回答了，我不知道openssh的行为从那时起是否发生了变化。我在测试: OpenSSH_8.6p1, OpenSSL 1.1.1g FIPS 21 Apr 2020

你可以这样做……

sudo /home/script.sh -opt1 > /tmp/script.out &

如果使用zsh，则使用程序执行&!是zsh特定于后台和否认进程的快捷方式，这样退出shell将使其继续运行。