From: Chris Boot <bootc@bootc.net>
To: netfilter-devel@vger.kernel.org
Cc: Chris Boot <bootc@bootc.net>, Eric Leblond <eric@regit.org>
Subject: [PATCH 0/2] Introductions, some tweaks to ulogd
Date: Sat, 11 May 2013 18:01:51 +0100 [thread overview]
Message-ID: <1368291713-40132-1-git-send-email-bootc@bootc.net> (raw)
Hi folks,
I am working on packaging ulogd-2.x for Debian, and currently have an initial
set of packages uploaded and waiting for ftpmaster review in the NEW queue.
I'd like to say hello to all folks involved with ulogd, and thanks for all the
hard work getting it to where it is. Hopefully we can work together and make
ulogd-2.x a first class citizen in Debian.
I intend to be a fully cooperative downstream maintainer, and to prove my
intentions here are a couple of patches that I've been working on for the next
upload of ulogd2.
The first patch simply fixes the deamon being able to nice() itself when run
with the --uid argument. Currently the code runs nice() after setuid(); this
fails to increase its priority as it is no longer root. The patch simply moves
the code around a little to fix this.
The second patch adds a --pidfile option to ulogd, which enables it to write a
PID file to somewhere like /var/run (or just /run). This is very useful within
init scripts to make sure you're sending signals to the correct process.
Cheers,
Chris
Chris Boot (2):
ulogd: Perform nice() before giving up root
ulogd: Implement PID file writing
src/ulogd.c | 89 +++++++++++++++++++++++++++++++++++++++++++++++++++++------
1 file changed, 81 insertions(+), 8 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-05-11 17:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-11 17:01 Chris Boot [this message]
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
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=1368291713-40132-1-git-send-email-bootc@bootc.net \
--to=bootc@bootc.net \
--cc=eric@regit.org \
--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).