From: Eric Leblond <eric@regit.org>
To: Chris Boot <bootc@bootc.net>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH v2] ulogd: Implement PID file writing
Date: Sun, 19 May 2013 21:19:38 +0200 [thread overview]
Message-ID: <1368991178.14976.4.camel@ice-age.regit.org> (raw)
In-Reply-To: <5195DD43.50608@bootc.net>
[-- Attachment #1: Type: text/plain, Size: 544 bytes --]
Hi,
Le vendredi 17 mai 2013 à 08:33 +0100, Chris Boot a écrit :
> On 12/05/13 13:47, Chris Boot wrote:
> > The deamon currently does not have the ability to write a PID file to track its
> > process ID. This is very useful to an init script and to ensure there is only
> > one running instance. This patch implements this functionality.
> >
> > Signed-off-by: Chris Boot <bootc@bootc.net>
I've applied this patch to my tree and made incremental modification to
fix some issues as explained in the upcoming patch.
BR,
--
Eric
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2013-05-19 19:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-11 17:01 [PATCH 0/2] Introductions, some tweaks to ulogd Chris Boot
2013-05-11 17:01 ` [PATCH 1/2] ulogd: Perform nice() before giving up root Chris Boot
2013-05-17 7:34 ` Chris Boot
2013-05-17 8:28 ` Eric Leblond
2013-05-11 17:01 ` [PATCH 2/2] ulogd: Implement PID file writing Chris Boot
2013-05-11 19:21 ` Pablo Neira Ayuso
2013-05-11 20:27 ` Chris Boot
2013-05-12 0:48 ` Pablo Neira Ayuso
2013-05-12 8:11 ` Chris Boot
2013-05-12 9:34 ` Pablo Neira Ayuso
2013-05-12 9:38 ` Chris Boot
2013-05-12 10:50 ` Pablo Neira Ayuso
2013-05-12 19:34 ` Eric Leblond
2013-05-12 9:47 ` Eric Leblond
2013-05-12 10:08 ` Chris Boot
2013-05-12 10:49 ` Pablo Neira Ayuso
2013-05-12 9:53 ` Eric Leblond
2013-05-12 10:59 ` Chris Boot
2013-05-12 12:47 ` [PATCH v2] " Chris Boot
2013-05-17 7:33 ` Chris Boot
2013-05-19 19:19 ` Eric Leblond [this message]
2013-05-19 19:22 ` [Ulogd PATCH] Improve pid file handling Eric Leblond
2013-05-22 9:22 ` Chris Boot
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=1368991178.14976.4.camel@ice-age.regit.org \
--to=eric@regit.org \
--cc=bootc@bootc.net \
--cc=netfilter-devel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).