9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] 'stuck' windows.
Date: Sun, 22 Jun 2008 07:47:43 -0400	[thread overview]
Message-ID: <5902bcf4c776111c8c09f50a06e1c8ea@quanstro.net> (raw)
In-Reply-To: <ba0d3bc70806220045x312ad75bo4714767ebcba9ba9@mail.gmail.com>

> On 6/22/08, Russ Cox <rsc@swtch.com> wrote:
>> 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.
>>
>> Probably the various dossrv'ing scripts should run
>>
>> 	dossrv </dev/null >/dev/null >[2=1]
>
> But that's what 9fat: does (well, not literally, since it does 'dossrv
>>/dev/null </dev/null >[2]/dev/null', but it means the same). So then
> dossrv shouldn't be holding the window's /dev/cons open, right?

russ is should be correct.

i think that dossrv's quirks are surprising.  the
redirection in 9fat: is superfluous since 9fat opens
/dev/null on fds 0 and 1 and it makes this surprise
move for fd 2:

	if(!chatty){
		close(2);
		open("#c/cons", OWRITE);
	}

that's downright antisocial.  maybe there's a good
reason.  but i can't think of one now.

- erik




  reply	other threads:[~2008-06-22 11:47 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
2008-06-22  7:45   ` Sander van Dijk
2008-06-22 11:47     ` erik quanstrom [this message]
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=5902bcf4c776111c8c09f50a06e1c8ea@quanstro.net \
    --to=quanstro@quanstro.net \
    --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).