From: Alasdair G Kergon <agk@redhat.com>
To: lvm-devel@redhat.com
Subject: [PATCH] pid files cleanup
Date: Fri, 9 Jul 2010 14:20:18 +0100 [thread overview]
Message-ID: <20100709132017.GZ22664@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <4C36E604.6090106@redhat.com>
On Fri, Jul 09, 2010 at 11:04:04AM +0200, Fabio M. Di Nitto wrote:
> - create_lockfile can probably use fcntl_lock_file, but I am not
> entirely sure about its behavior yet (specially the waiting note in the
> header), so I choose a safe path for now and use a known (to me)
> implementation.
Don't worry about that now if the code is moving to libdevmapper anyway.
Sharing it just brings in the existing code that can create the
directory path if it's not there, but it really always should be!
Alasdair
prev parent reply other threads:[~2010-07-09 13:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 9:04 [PATCH] pid files cleanup Fabio M. Di Nitto
2010-07-09 13:09 ` Alasdair G Kergon
2010-07-09 13:18 ` Fabio M. Di Nitto
2010-07-09 13:11 ` Alasdair G Kergon
2010-07-09 13:20 ` Fabio M. Di Nitto
2010-07-09 13:28 ` Alasdair G Kergon
2010-07-09 13:20 ` Alasdair G Kergon [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=20100709132017.GZ22664@agk-dp.fab.redhat.com \
--to=agk@redhat.com \
--cc=lvm-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.