From: "Russ Cox" <rsc@swtch.com>
To: 9fans@9fans.net
Subject: Re: [9fans] 'stuck' windows.
Date: Sat, 21 Jun 2008 20:50:45 -0400 [thread overview]
Message-ID: <20080622004931.A05691E8C22@holo.morphisms.net> (raw)
In-Reply-To: <ba0d3bc70806211121y59be548ycb41a958c10a8ac5@mail.gmail.com>
> When I open a window in rio, run 9fat:, and then exit, the window gets
> 'stuck'. That is, it just sits there, I can't type anything in it
> anymore.
> Apparently, it is waiting for dossrv to exit (which gets started by
> 9fat:): when I open a second window, and run 'kill dossrv | rc', the
> first window disappears.
It is not waiting for dossrv to exit,
so much as it is waiting for all the open
file descriptors referring to that window's
/dev/cons to be closed. Dossrv just happens
to be the one holding them.
The window is reference-counted, and
there are still references. Try this in a window:
{sleep 2; echo hello world; sleep 2}& exit
Probably the various dossrv'ing scripts should run
dossrv </dev/null >/dev/null >[2=1]
but then you do lose any errors from dossrv.
On the other hand, if dossrv does error out
you'd still get an error from mount about #s/dos
not existing, so you would get *some* output.
> Am I doing something wrong (is there a way I can actually exit said
> window without killing dossrv)?
No, and no. Well, except for starting dossrv
differently.
> Has it always been this way
I think it has.
Russ
next prev parent reply other threads:[~2008-06-22 0:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-21 18:21 Sander van Dijk
2008-06-21 21:39 ` erik quanstrom
2008-06-22 7:36 ` Sander van Dijk
2008-06-21 23:48 ` Pietro Gagliardi
2008-06-22 0:44 ` Russ Cox
2008-06-22 0:50 ` Russ Cox [this message]
2008-06-22 7:45 ` Sander van Dijk
2008-06-22 11:47 ` erik quanstrom
2008-06-22 11:59 ` erik quanstrom
2008-06-22 11:50 ` Russ Cox
2008-06-22 12:58 ` Sander van Dijk
2008-06-22 14:22 ` Russ Cox
2008-06-23 14:50 ` Dave Eckhardt
2008-06-24 8:53 ` Sander van Dijk
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=20080622004931.A05691E8C22@holo.morphisms.net \
--to=rsc@swtch.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).