From: Porlock <porlock@mailinator.com>
To: 9fans@9fans.net
Subject: [9fans] Fileserver doesn't exit when it should
Date: Fri, 8 Aug 2014 11:30:32 +0100 [thread overview]
Message-ID: <53E4A6C8.2040902@mailinator.com> (raw)
Here is some behaviour which I don't understand. Something seems to be
preventing a fileserver process from exiting (since it doesn't receive
end-of-file on its 9p pipe).
To see this, open a new rio window and enter the following commands :-
ramfs -m /n/junk
cp /bin/echo /n/junk
/n/junk/echo hello
unmount /n/junk
Now try to close the rio window, by typing ^D at the prompt. The
window will not close. Further, the ramfs server is still running.
It must be killed manually (from another window), and then the window
will close.
I don't think this has anything to do with ramfs, since I tried the
same commands with a completely different ram filesystem server, and
it exhibited the same behaviour.
This behaviour doesn't happen on 9front, which behaves as you would
expect, with the file server exiting on unmount, and the window
closing on ^D.
next reply other threads:[~2014-08-08 10:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 10:30 Porlock [this message]
2014-08-08 14:02 ` erik quanstrom
2014-08-08 14:17 ` cinap_lenrek
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=53E4A6C8.2040902@mailinator.com \
--to=porlock@mailinator.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).