public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Again some "headless" stuff/question
Date: Tue, 7 Oct 2014 12:45:33 +0100	[thread overview]
Message-ID: <20141007124533.2a2b2c0f@hactar.digimed.co.uk> (raw)
In-Reply-To: <20141005043455.GA3856@solfire>

[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]

On Sun, 5 Oct 2014 06:34:55 +0200, meino.cramer@gmx.de wrote:

> for starting and running a script on a headless system for me "nohup"
> works perfectly.
> For interactive session via ssh screen/tmux turned out to be the
> solution to detach from jobs started from the commandline.
> Both are hints/help I received from the community here. :)
> Thank you very much !!! :)))
> 
> Since the screen/tmux thingie is THAT convenient I would like to start
> this as the default when logging in via ssh.
> I could write a script which is started by the shell (zsh) which in 
> turn is started as part of the login process.
> Screen would start another shell and TADA!...
> But this is an embedded system...
> 
> The result should be a running screen session right after login via
> ssh.
> 
> Is there any "shorter path" to what I am trying to do -- without the
> cascade of shells which do nothing but waiting of the child process to
> end?

I have this in ~/.zshrc.

if [[ "${TERM}" != "screen" ]] && [[ -z "${STY}" ]] && [[ ! -f ~/.noscreen ]]; then
    screen -xRR && exit
    fi


-- 
Neil Bothwick

Last words of a Windows user: = Where do I have to click now? - There?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  parent reply	other threads:[~2014-10-07 11:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-05  4:34 [gentoo-user] Again some "headless" stuff/question meino.cramer
2014-10-05 12:33 ` thegeezer
2014-10-05 14:10   ` meino.cramer
2014-10-07 11:45 ` Neil Bothwick [this message]
2014-10-07 16:46   ` meino.cramer
2014-10-07 20:16     ` Neil Bothwick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141007124533.2a2b2c0f@hactar.digimed.co.uk \
    --to=neil@digimed.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox