From: William Staniewicz <wstan@localhostnl.demon.nl>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] stopping sleep and aux/listen
Date: Fri, 29 Dec 2000 07:46:09 -0500 [thread overview]
Message-ID: <20001229064935.06988199E3@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 191 bytes --]
Yes, it looks like just running ftpfs will work fine keeping
the connection alive. I guess I just presumed I would need
to be doing something there to keep from appearing
idle.
Bill
[-- Attachment #2: Type: message/rfc822, Size: 1703 bytes --]
From: Scott Schwartz <schwartz@bio.cse.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] stopping sleep and aux/listen
Date: Thu, 28 Dec 2000 17:41:01 -0500
Message-ID: <20001228224102.11620.qmail@g.bio.cse.psu.edu>
| You can't kill this except by killing
| the rc that is running the while loop.
ftpfs used to send NOOPs once in a while. Isn't that sufficient to
keep the connection alive?
next reply other threads:[~2000-12-29 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-29 12:46 William Staniewicz [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-28 15:23 William Staniewicz
[not found] <rsc@plan9.bell-labs.com>
2000-12-28 9:33 ` Russ Cox
2000-12-28 22:41 ` Scott Schwartz
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=20001229064935.06988199E3@mail.cse.psu.edu \
--to=wstan@localhostnl.demon.nl \
--cc=9fans@cse.psu.edu \
/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).