From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] drawterm dies when my mac book sleeps by 9p design?
Date: Sun, 6 Mar 2011 19:31:34 -0800 [thread overview]
Message-ID: <20110307033134.E0E7DB835@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Sun, 06 Mar 2011 21:34:58 EST." <58b61128ec119c9e719f198844449401@brasstown.quanstro.net>
On Sun, 06 Mar 2011 21:34:58 EST erik quanstrom <quanstro@quanstro.net> wrote:
> > Is this how 9p currently behaves or is there some settings somewhere
> > that will help prevent it? Is there a thread that have already
> > discussed
>
> it's actually tcp that's timing out, not 9p.
>
> this is how almost all connection-based protocols behave.
> typically there are keep-alive packets set every so often.
> and if the last time a packet was received from the other
> side was too long ago, the connection is declared defunct
> and closed.
>
> there may be some controls determining how soon to turn
> off the wifi that may be of some help.
You don't need to mess with the wifi. Just do
$ sysctl -w net.inet.tcp.always_keepalive=0
This will prevent the stack from sending any keepalive packets
on its own. But this will *not* help if the higher level
protocol generates such packets.
next prev parent reply other threads:[~2011-03-07 3:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 0:35 Fernan Bolando
2011-03-07 2:34 ` erik quanstrom
2011-03-07 3:31 ` Bakul Shah [this message]
2011-03-07 3:34 ` erik quanstrom
2011-03-07 4:15 ` Bakul Shah
2011-03-07 4:17 ` erik quanstrom
2011-03-07 4:25 ` ron minnich
2011-03-07 4:44 ` Bakul Shah
2011-03-07 4:51 ` erik quanstrom
2011-03-07 5:38 ` Bakul Shah
2011-03-07 4:49 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-03-07 5:00 ` erik quanstrom
2011-03-07 8:54 ` Anthony Sorace
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=20110307033134.E0E7DB835@mail.bitblocks.com \
--to=bakul@bitblocks.com \
--cc=9fans@9fans.net \
/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).