From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Marzinski Subject: Re: [PATCH v2] multipath: add find_multipaths feature. Date: Thu, 1 Sep 2011 15:43:54 -0500 Message-ID: <20110901204354.GN11793@ether.msp.redhat.com> References: <20110725185758.GA1368@ether.msp.redhat.com> <20110901025518.GD11793@ether.msp.redhat.com> <1314861263.14056.89.camel@lapoo.opensvc.com> <20110901125720.GF11793@ether.msp.redhat.com> <20110901142106.GG11793@ether.msp.redhat.com> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20110901142106.GG11793@ether.msp.redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: christophe.varoqui@opensvc.com, device-mapper development List-Id: dm-devel.ids On Thu, Sep 01, 2011 at 09:21:06AM -0500, Benjamin Marzinski wrote: > > although it looks like the systemd folks have made /run a tmpfs > filesystem, and /var/run a pointer to it (at least in Fedora), so I > guess I'm not opposed to moving things back to /var/run anymore. > When I wrote this, I had just finished writing an email about how /var/run being on tmpfs made it o.k. for pidfiles, and my brain had obviously not switched gears. While I have no problem with pidfiles on /var/run, storing permanent configuration files on it is obviously not an option if it is a tmpfs filesystem. -Ben