From: Manoj Srivastava <srivasta@datasync.com>
Cc: ding@gnus.org
Subject: Re: sending mail (!) thru ssh
Date: 31 Mar 1998 12:19:09 -0600 [thread overview]
Message-ID: <87emzik9k2.fsf@tiamat.datasync.com> (raw)
In-Reply-To: Stefan Waldherr's message of "31 Mar 1998 11:21:32 -0500"
Hi,
Yes, ssh seems to be quite robust that way. I too use diald,
and have a fairly aggressive pull down timeouts, so i often have
remote seession on when diald pulls the connection down. Typing in
the window reconnects, and all I have is a delay (don't know what
happens if the remote shell generates data in the meanwhile).
manoj
--
Charity: a thing that begins at home and usually stays there.
Manoj Srivastava <srivasta@acm.org> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
next prev parent reply other threads:[~1998-03-31 18:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-30 14:13 Stefan Waldherr
1998-03-30 14:39 ` Kai Grossjohann
1998-03-30 14:48 ` Stefan Waldherr
1998-03-30 18:35 ` David Hedbor
1998-03-31 16:21 ` Stefan Waldherr
1998-03-31 18:19 ` Manoj Srivastava [this message]
1998-03-31 20:13 ` Lars Balker Rasmussen
1998-03-31 21:32 ` Manoj Srivastava
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=87emzik9k2.fsf@tiamat.datasync.com \
--to=srivasta@datasync.com \
--cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).