All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei B <andrixnet@yahoo.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Chicken and egg problem with multipath-tools
Date: Sun, 03 Mar 2013 23:01:37 +0200	[thread overview]
Message-ID: <5133BA31.6080208@yahoo.com> (raw)
In-Reply-To: <kgvcv1$l3e$4@ger.gmane.org>

Well, that would be an idea. However, multipathd has the pidfile
hardcoded. It cannot be changed at runtime, nor can it be disabled.

I know, I could compile it with a different hardcoded path, but that's
really a bad idea, because then if multipathd were to be restarted
anytime later after boot, it would then fail because of the same reason.


On 2013-03-03 01:42 PM, Gabriel de Perthuis wrote:
>> The problem is that multipathd wants to create a PID file under /var
>> (which is at this time readonly). This fails and multipathd fails to
>> start.
> Distros handle this by putting pidfiles in /run, a tmpfs set up at early 
> boot. There might be some magic to ensure that later mounts don't shadow 
> it.
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel

  reply	other threads:[~2013-03-03 21:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-02 10:43 Chicken and egg problem with multipath-tools Andrei B.
2013-03-03 11:42 ` Gabriel de Perthuis
2013-03-03 21:01   ` Andrei B [this message]
2013-03-04 10:49     ` Bryn M. Reeves
2013-03-04  6:54 ` Hannes Reinecke
2013-03-04 11:00   ` Andrei B.
2013-03-04 11:13     ` Hannes Reinecke
2013-03-04 11:27       ` Bryn M. Reeves
2013-03-04 10:54 ` Bryn M. Reeves

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=5133BA31.6080208@yahoo.com \
    --to=andrixnet@yahoo.com \
    --cc=dm-devel@redhat.com \
    /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 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.