all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guix-devel@gnu.org
Subject: Re: File systems
Date: Wed, 14 May 2014 19:12:40 +0200	[thread overview]
Message-ID: <87bnv0i8s7.fsf@gnu.org> (raw)
In-Reply-To: <87eh01titd.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 10 May 2014 23:39:10 +0200")

ludo@gnu.org (Ludovic Courtès) skribis:

> To support clean unmounting of file systems upon shutdown, special dmd
> services are added to the graph (see (gnu services base)):
>
>   • ‘root-file-system’, whose stop action is to remount / read-only;
>     this is the last service that is stopped when shutting down.
>
>   • For each file system not needed for boot, there’s a
>     ‘file-system-XYZ’ service depending only on ‘root-file-system’, with
>     a stop action to unmount XYZ.
>
>   • ‘user-processes’, which depends on all the ‘file-system-XYZ’ and on
>     ‘root-file-system’.  Its stop action is to kill all the processes
>     still running.  All the services that spawn processes must depend on
>     it.  The goal is to make sure the file systems can actually be
>     unmounted.

There was the complication that when root is a user-space file system,
like unionfs-fuse (as in the VM produced by ‘guix system vm’),
‘user-processes’ would kill it, thus leading to breakage just before
reboot.

Commit 7d57cfd fixes that by providing a mechanism to tell
‘user-processes’ which processes must remain alive during shutdown.  In
the unionfs-fuse case, the initrd code just writes the PID of
unionfs-fuse to /etc/dmd/do-not-kill, and ‘user-processes’ honors that file.

Ludo’.

      reply	other threads:[~2014-05-14 17:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-10 21:39 File systems Ludovic Courtès
2014-05-14 17:12 ` Ludovic Courtès [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=87bnv0i8s7.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.