| 1 |
... I just hope the remote system isn't running systemd, if so, you have to |
| 2 |
do some additional tweaking before screen or tmux work. I know someone who |
| 3 |
was bitten hard by this. Apparently systemd by default closes all running |
| 4 |
processes of a user on logout. |
| 5 |
|
| 6 |
Il giorno ven 24 apr 2020 alle ore 09:47 Raffaele BELARDI < |
| 7 |
raffaele.belardi@××.com> ha scritto: |
| 8 |
|
| 9 |
> Hello, |
| 10 |
> |
| 11 |
> |
| 12 |
> |
| 13 |
> I am able to ssh into a remote system that I would like to update. I’d |
| 14 |
> like to run emerge without keeping the local system connected for the whole |
| 15 |
> duration of the update (probably several days). Is it possible to: |
| 16 |
> |
| 17 |
> |
| 18 |
> |
| 19 |
> - ssh remote_machine |
| 20 |
> |
| 21 |
> - emerge -uDvN world |
| 22 |
> |
| 23 |
> - background and detach in some way the emerge process |
| 24 |
> |
| 25 |
> - logout from ssh |
| 26 |
> |
| 27 |
> - several days later, ssh into the remote_machine, reattach the emerge and |
| 28 |
> check the output or continue the emerge |
| 29 |
> |
| 30 |
> |
| 31 |
> |
| 32 |
> Thanks, |
| 33 |
> |
| 34 |
> |
| 35 |
> |
| 36 |
> raffaele |
| 37 |
> |
| 38 |
> |
| 39 |
> |
| 40 |
> PS I’ll do it _*after*_ openssh update. |
| 41 |
> |
| 42 |
> |
| 43 |
> |
Archives