[dm-devel] [PATCH 01/17] multipathd: use /run instead of /var/run

[John Stoffel]

>>>>> "Benjamin" == Benjamin Marzinski <bmarzins at redhat.com> writes:

Benjamin> On Tue, Mar 29, 2016 at 09:57:25AM -0400, John Stoffel wrote:
>> 
Benjamin> /var/run is now usually a symlink to /run.  If /var is on a separate
Benjamin> filesytem, when multipathd starts up, it might end up writing to
Benjamin> /var/run before the /var filesytem is mounted and thus not have its
Benjamin> pidfile accessible at /var/run afterwards.  On most distrubutions /run
Benjamin> is now a tmpfs and should always be available before multipathd is
Benjamin> started, so multipath should just write there directly, instead of
Benjamin> through the symlink.
>> 
>> I'm not sure I agree with this, it really smells more like a
>> distribution problem, than a multipathd problem.  If multipathd starts
>> up in an initramfs, how does it get reset to the proper /var/run or
>> /run directory then?

Benjamin> Huh? /run is a tmpfs on almost all distros now. It gets
Benjamin> remounted when you switch the root from the initramfs, but
Benjamin> it doesn't go away. So there isn't a "proper" /run that
Benjamin> appears later. /var/run just gets symlinked to it.

Gah!  I apologize for the noise, I did a quick check on some RHEL5/6
systems (which are ancient I agree!) and didn't look at newer
debian/mint systems as well.  And I do see that /run is there.  

John