On Wed, Jun 01, 2016 at 10:25:32AM +0100, Tom Hughes wrote:
On 01/06/16 10:20, Bastien Nocera wrote:
>>On Sun, May 29, 2016 at 06:51:20PM -0600, Chris Murphy wrote:
>>>So there's tmux, screen, curl, wget, and probably quite a few others
>>>that don't necessarily get daemonized that are probably affected.
>>I would really like to see a solution whereby tmux and screen _just
>>work_ without any required changes to user behavior. They're basically
>>commands which _indicate_ "I want a new session that persists".
>Really? The only times I ever used it was to access serial consoles with
>a better emulation than separate apps.
You've obviously never had to run something that's going to take
hours or days to complete on a remote server and not wanted it to
abort half way through because of a network glitch then.
That's when I use screen, either just setting running something in
the background, or leaving it connected but knowing it will continue
if anything goes wrong and I can just reattach from a new login.
I'm using 'screen /dev/ttyUSBX 115200' to monitor serial consoles
while I'm logged out :-)
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch