On 07/10/2015 06:45, Aero Maxx wrote:
On 06/10/2015 22:07, Rick Stevens wrote:
> On 10/06/2015 01:29 PM, Aero Maxx wrote:
>> Hello,
>>
>> I use the screen tool quite a lot for running processes that I need to
>> complete but aren't able to be connected to the box for the length of
>> time it takes for it to complete.
>>
>> I've noticed the last few months, (cant remember how long exactly but
>> its been less than a year i'd say) that when I either create a
>> screen or
>> resume an existing screen, when either of these are exitted the output
>> is still displayed within the window that I went to when I detacted
>> from
>> the screen.
>>
>> I cant recall anything that I may have done to stop the screen from
>> clearing when I detacted from them.
>>
>> I was just wondering if anyone was able to shed any light on why it
>> might be doing this.
>
> Are you starting screen, then issuing the command inside the screen
> session or are you doing "screen somecommand" and then detaching once
> the command has started?
> ----------------------------------------------------------------------
> - Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
> - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
> - -
> - I'm afraid my karma just ran over your dogma -
> ----------------------------------------------------------------------
I am starting the screen, then typing in the command inside the screen
session, then I wait a bit to check its running as intended then
detach from the screen afterwards.
I didn't know I could do "screen somecommand" and then detach.
Thanks,
Daniel.
I just tried the "screen some command" and then detach and that
does the
same as doing screen, then typing in the command in the window then
detaching afterwards.
Thanks,
Daniel.
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus