All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Alexandre Oliva <oliva@gnu.org>
Cc: ceph-devel@vger.kernel.org
Subject: Re: [PATCH] daemons: write pid file even when told not to daemonize
Date: Thu, 28 Aug 2014 10:09:28 +0200	[thread overview]
Message-ID: <53FEE3B8.4070902@dachary.org> (raw)
In-Reply-To: <or7g1tawy9.fsf@free.home>

[-- Attachment #1: Type: text/plain, Size: 902 bytes --]

Hi Alexandre,

Changing this behavior is not backward compatible but it is indeed more intuitive. Has it been a significant inconvenience so far ?

Cheers

On 28/08/2014 09:35, Alexandre Oliva wrote:
> On Jul 31, 2014, Sage Weil <sweil@redhat.com> wrote:
> 
>> On Thu, 31 Jul 2014, Loic Dachary wrote:
>>> Hi Alexandre,
>>>
>>> With this patch ceph-osd -f will try to create the default pid file : 
>>> this is a non backward compatible change. Maybe there is a way for 
>>> systemd to capture the pid of the process and store it instead of 
>>> requiring the deamon to create the pid file ?
> 
>> Do we need the pid file at all when we aren't using sysinit?
> 
> My own monitoring scripts use it, and ceph stop use it as well.  I was
> surprised we were not creating them in spite of an explicit command line
> option to do so.
> 

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

  reply	other threads:[~2014-08-28  8:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-31  2:08 [PATCH] daemons: write pid file even when told not to daemonize Alexandre Oliva
2014-07-31  4:18 ` Loic Dachary
2014-07-31  4:30   ` Sage Weil
2014-08-28  7:35     ` Alexandre Oliva
2014-08-28  8:09       ` Loic Dachary [this message]
2014-08-29  6:41         ` Alexandre Oliva
2014-08-29  8:40           ` Loic Dachary
2014-09-04 19:48             ` Alexandre Oliva
2014-09-09 22:21 ` Sage Weil
2014-09-09 22:48   ` Loic Dachary
2014-09-09 22:54     ` Sage Weil
2014-09-12 10:22 ` Loic Dachary

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=53FEE3B8.4070902@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=oliva@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.
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.