l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2003 May 21 11:42

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] starting screen from shell startup script
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] starting screen from shell startup script

> On Wed, 21 May 2003, Mark K. Kim wrote:
>> So now I'm ready to learn screen.
> Ok...
>>  So I'm about to put screen in my startup script.
> ... but I don't see that this is necessary or even a good idea?
>> Except...
>> Once I login, it'll execute screen, which will run screen again, which
>> will run screen again, then again, etc. and it'll be caught in an
>> infinite
>> loop.  Or does it detect itself somehow?  Or do I play with my
>> bash_profile vs. bashrc thing?  How do I prevent it from running itself
>> recursively?
> Screen supports reconnection ("-r") after intentional ("-d") or
> unintentional (communication failure) disconnection... but you have to
> give it the right options before it will Do What You Want.  Personally, I
> like to re-use a single instance of screen.  It might be possible to
> automate management of that, but I would think you would know how to do
> that after doing it manually for awhile.
> If you do proceed to automate based on terminal type like ME suggests,
> and if you ssh between different machines or accounts, what will happen
> when you ssh into your other account and it sees that you are already
> using "screen" from the first account?  You might be better off not using
> screen locally when you connect to your remote account.  Thus, putting it
> into your local .profile could prove to be inconvenient.

Yep. I automated mine about 7 years ago, but decided after a few months
that it was easier to start it up manually. An intermediate step I
included was the -R so that it would continue if there was one to
continue, but found this was not a good idea when a screen session was
"available" for reconnection but had somehow become frozen. (SunOS v 4.x
with screen and admin upgraded libs/patched system while stuff was

I now go manual since I am most often reattaching to a screen session with
all my stuff running as it should.


vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
Appahost Applications
For a significant contribution towards our projector, and a generous donation to allow us to continue meeting at the Davis Library.