From: guillaume.quintard@gmail.com (Guillaume Quintard)
Subject: [sup-talk] Crashing ssh + sup, bad combo
Date: Fri, 21 Aug 2009 21:29:22 +0200 [thread overview]
Message-ID: <1e5fdab70908211229w2f11d11h4db7500a340b923b@mail.gmail.com> (raw)
In-Reply-To: <a412e2a70908211157vcd73cc6r4b401fd38f50902@mail.gmail.com>
On Fri, Aug 21, 2009 at 8:57 PM, Mark Alexander<marka at pobox.com> wrote:
> This isn't directly related, and you may already know about this, and
> apologies if that's the case... but I highly recommend running screen
> on the machine where you're running sup. ?That way you don't lose any
> work when your ssh connection drops for any reason.
>
Yup, I know, but screen isn't yet natural to me, and I tend to forgot
to use it :-)
--
Guillaume
next prev parent reply other threads:[~2009-08-21 19:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 16:00 Guillaume Quintard
2009-08-21 18:57 ` Mark Alexander
2009-08-21 19:29 ` Guillaume Quintard [this message]
2009-08-21 20:57 ` Rich Lane
2009-08-24 22:46 ` William Morgan
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=1e5fdab70908211229w2f11d11h4db7500a340b923b@mail.gmail.com \
--to=guillaume.quintard@gmail.com \
/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