| 2015-10-02 15:17:07 |
Sturm Flut |
bug |
|
|
added bug |
| 2015-10-05 15:55:49 |
Sam Bull |
description |
It would be nice if a Terminal session, e.g. with an SSH connection established to some server or running a local script that regularly gathers some data , could keep running in the background. |
Some commands that are run in the terminal should be run in the background. For example ssh to stop a session timing out, or compiling a program while doing other things on the phone.
A simple solution would be to give a lifecycle exception to the terminal app.
Another solution would be to use a special command that would run a command in the background. In the same manner that the sudo command runs any command as a different user, another command (e.g. runbg) could run any command as an external background running program.
This command might do something along the lines of forking the process so that it is not owned by the terminal app and thus not dependent on the terminal to keep running.
This solution giving the user more control without compromising the experience when background processing is not needed. |
|
| 2015-10-05 15:56:35 |
Sam Bull |
summary |
Keep Terminal session running in the background |
Terminal - running commands in the background |
|
| 2015-10-05 15:56:51 |
Sam Bull |
bug task added |
|
ubuntu-terminal-app |
|
| 2016-01-28 22:03:42 |
lgd |
bug |
|
|
added subscriber lgd |
| 2016-03-14 10:01:23 |
Cesar Herrera |
bug |
|
|
added subscriber Cesar Herrera |
| 2016-04-29 09:48:48 |
Sam Bull |
summary |
Terminal - running commands in the background |
Terminal - running process is paused and not restored |
|
| 2016-04-29 09:57:53 |
Sam Bull |
description |
Some commands that are run in the terminal should be run in the background. For example ssh to stop a session timing out, or compiling a program while doing other things on the phone.
A simple solution would be to give a lifecycle exception to the terminal app.
Another solution would be to use a special command that would run a command in the background. In the same manner that the sudo command runs any command as a different user, another command (e.g. runbg) could run any command as an external background running program.
This command might do something along the lines of forking the process so that it is not owned by the terminal app and thus not dependent on the terminal to keep running.
This solution giving the user more control without compromising the experience when background processing is not needed. |
When the terminal goes out of focus with a long running process, the process is paused and not restored when the terminal comes back into focus.
There are 2 different camps of thought on how to solve this.
***
The first is to allow these processes to run in the background:
A simple solution would be to give a lifecycle exception to the terminal app.
Another solution would be to use a special command that would run a command in the background. In the same manner that the sudo command runs any command as a different user, another command (e.g. runbg) could run any command as an external background running program.
This command might do something along the lines of forking the process so that it is not owned by the terminal app and thus not dependent on the terminal to keep running.
This solution giving the user more control without compromising the experience when background processing is not needed.
***
The second solution is to automatically do the equivalent of running the 'fg' command when the terminal is back in focus. This allows many long running processes to keep working seamlessly while not compromising the battery and lifecycle design of the OS. In my experience, I was able to 'fg' an ssh command after around 40 mins of the process being paused, and continue with my SSH session unhindered. |
|
| 2017-01-13 09:27:53 |
Florian Boucault |
ubuntu-terminal-app: importance |
Undecided |
High |
|
| 2017-01-13 09:27:56 |
Florian Boucault |
ubuntu-terminal-app: status |
New |
Confirmed |
|
