From: "Tyler Spivey" <tspivey8@softhome.net>
To: speakup@braille.uwo.ca
Subject: Re: screen question
Date: Mon, 9 Jun 2003 09:06:53 -0700 [thread overview]
Message-ID: <001001c32ea1$3260c180$691817cf@130SetBC01> (raw)
In-Reply-To: <Pine.LNX.4.44.0306061400270.13490-100000@igueths>
i'm not sure on that last point about attaching to an already existing
process.
you can run that application under screen though, and re-attach anywhere.
even if you haven't detached it (if yo u've forgotten, etc), as long as it's
in a screen and that screen isn't killed off or the computer hasn't been
powered down due to a power failiure or other unforseen circumstances.
----- Original Message -----
From: "Igor Gueths" <igueths@attbi.com>
To: <speakup@braille.uwo.ca>
Sent: Friday, June 06, 2003 11:01 AM
Subject: screen question
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi all. I was rtfm on screen, and it seems that you can only detach and
> re-attach existing screen sessions. The console I want to bind to that has
> an ap running on it isn't running under screen. Can i still use screen to
> redirect stdout on tty2 to my telnet/ssh console?
>
> May you code in the power of the source,
> may the kernel, libraries, and utilities be with you,
> throughout all distributions until the end of the epoch.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.2 (GNU/Linux)
> Comment: Made with pgp4pine 1.75-6
>
> iD8DBQE+4NcPGT7f58lCbH0RAuvNAKCijVAifSmzt0npgshkSdKIv6We/wCfWYc+
> d8GsJ9fCBH2OSxMV+kL7FXw=
> =XvIL
> -----END PGP SIGNATURE-----
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
prev parent reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
Igor Gueths
` Tyler Spivey [this message]
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='001001c32ea1$3260c180$691817cf@130SetBC01' \
--to=tspivey8@softhome.net \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).