9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Pietro Gagliardi <pietro10@mac.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 'stuck' windows.
Date: Sat, 21 Jun 2008 19:48:49 -0400	[thread overview]
Message-ID: <5897EA6C-79AE-47DA-ADD2-B26215B04C53@mac.com> (raw)
In-Reply-To: <ba0d3bc70806211121y59be548ycb41a958c10a8ac5@mail.gmail.com>

On Jun 21, 2008, at 2:21 PM, Sander van Dijk wrote:
> This (being unable to exit the window without killing dossrv) seems a
> bit strange to me. I can of course destroy the window using the
> 'Delete' option in rio's menu, but I think that's not the 'right' way
> to do it.
> Am I doing something wrong (is there a way I can actually exit said
> window without killing dossrv)?
> Has it always been this way (I believe I vaguely remember that
> somewhere in the past I could exit from the window that started dossrv
> without problems)?

It's happened to me quite often. I think rc should kill all
subprocesses on exit, but I don't think dossrv handles the hangup
note: adding

	postnote(NPGROUP, getpid(), "hangup");

to plan9.c:Exit() and trying

	a: & exit # no floppy disk drive (QEMU) keeps a: hanging

does nothing. What I do is I put 9fat:, 9fs wiki, 9fs sources in my
profile to run automatically.

How I wish Plan 9 had kill -9! The kernel uses the note

	sys: killed

internally, but notify(2) doesn't say so. I wonder...




  parent reply	other threads:[~2008-06-21 23:48 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 [this message]
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
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=5897EA6C-79AE-47DA-ADD2-B26215B04C53@mac.com \
    --to=pietro10@mac.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).