9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Benjamin Riefenstahl <b.riefenstahl@turtle-trading.net>
To: Steve Simon <steve@quintile.net>
Cc: 9front@9front.org
Subject: Re: [9front] Invers of partfs
Date: Mon, 14 Feb 2022 20:06:00 +0100	[thread overview]
Message-ID: <87r185s1yf.fsf@turtle-trading.net> (raw)
In-Reply-To: <87iltlmxul.fsf@turtle-trading.net> (Benjamin Riefenstahl's message of "Fri, 11 Feb 2022 12:44:34 +0100")

Hi Steve, all.

> Steve Simon writes:
>> probably the easiest would be to put your tests in a script with
>> “rfork ne” at the top.
>>
>> this will ensure that when your script ends the namespace and
>> environment will evaporate. partfs will also close as its input is
>> closed as part of the namspace going.

Interestingly, partfs (i.e. the block device) and the filesystem mount
itself do go away as expected, but the cwfs64x processes (some 20 or 21
processes) do not.  They require "echo halt >> /srv/servicename" to end
themself.  Is that expected or is it a bug?

What I do, just for background: I have a diskimage with partitions for a
cwfs file system on it.  I run partfs, cwfs64x, and mount to get at the
contents of the file system.

When I run that inside a process with "rfork ne", the service created by
cwfs64x is visible from another rio window, but not the block device
created by partfs and not the mounted filesystem.  So it's consistent in
that way.

benny

      reply	other threads:[~2022-02-15  9:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 17:42 Benjamin Riefenstahl
2022-02-10 19:07 ` Steve Simon
2022-02-11 11:44   ` Benjamin Riefenstahl
2022-02-14 19:06     ` Benjamin Riefenstahl [this message]

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=87r185s1yf.fsf@turtle-trading.net \
    --to=b.riefenstahl@turtle-trading.net \
    --cc=9front@9front.org \
    --cc=steve@quintile.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).